Start with an inventory of the affected URLs
Collect the URLs, saved title elements, visible main headings and service summaries in one table. Include the language and the template used by each page. Group identical titles after trimming accidental whitespace, but keep the original text for comparison. This creates a repair list instead of relying on a few remembered search results.
Check the served HTML as well as the title entered in your content system. A title field can be correct while a template replaces it with a generic default. Record which version you observed and when. A repeated title is a useful signal to investigate; it does not by itself prove that the underlying services are duplicates.
Confirm that the services actually differ
For each pair, identify the customer task, deliverable and meaningful scope difference. A website maintenance service and a website migration service can warrant separate pages even if both currently say Website services. Write one sentence explaining the distinction using information already visible on each page.
If you cannot find a real distinction, return the pair for a content and URL review. Adding different words to nearly identical offers does not resolve that underlying problem. Conversely, do not redirect a useful service page merely to remove a title warning. Keep the decision about content consolidation separate from this metadata repair.
Fix the source of the repeated default
Trace the title to its owner: a page field, a reusable template, a localization fallback or another metadata generator. Test one representative page before editing the whole group. A template correction may repair many missing overrides, while a bulk replacement could erase titles that were already carefully written.
Google recommends descriptive, concise titles and discourages repeated boilerplate. Use the service distinction as the main wording and add the brand consistently where useful. Numeric suffixes such as Service 1 and Service 2 make strings different without explaining the offer. Avoid adding locations, credentials or benefits that the page cannot support.
Work through a clearly hypothetical example
Imagine an agency with two pages both titled Website services | Example Agency. One describes ongoing updates and maintenance; the other describes moving an existing website to a new hosting environment. These are invented pages used to demonstrate the editing process, not a customer case study.
Possible replacements are Website maintenance | Example Agency and Website migration | Example Agency, provided those labels match the actual scope. Give the Arabic editions natural equivalents supported by their own content. Keep the existing URLs unless a separate review identifies a reason to change them; a title edit alone does not require a migration.
Verify the repair without promising the displayed search title
After publishing, fetch each affected page and confirm that the intended title is present once in the document head. Recheck language, main heading and the service summary. Repeat the inventory to find remaining defaults and inspect a page outside the affected group to catch an overly broad template change.
Save the before-and-after values, the reason for each distinction and the verification date. Google can generate title links from several page and reference signals, so a saved title is not a promise of exact search-result wording. Investigate an unexpected displayed title with the query and observation date rather than repeatedly rewriting correct metadata.