Direct answer: When the same SEO defect appears across a URL pattern, fix the template, routing rule, navigation component, or generator that creates it. Page-by-page edits are temporary. A complete fix names the shared source, implementation owner, rollback path, and recrawl test.
Some SEO problems can be fixed in a CMS field. Others are generated by a shared template, routing rule, navigation component, or sitemap process. In those cases, editing individual pages treats the symptom while the generator keeps recreating it. The GPT-6 Astra website-audit field test shows how repository access helped trace five such defects across backend, routing, accessibility, and schema code.
The right workflow is consistent: identify the visible symptom, locate the shared source, change it with an appropriate developer or site owner, then crawl the rendered site again. Below are five common examples with a detection method, likely fix location, and validation step.
Use this implementation map
| Repeated symptom | Likely shared source | Validation after deployment |
|---|---|---|
| Duplicate titles | Page template or content-to-template data binding | Crawl the affected pattern and confirm distinct, descriptive titles |
| Wrong canonicals | Head template, routing rule, or URL helper | Sample final 200 URLs and confirm the intended canonical in rendered HTML and URL Inspection |
| Uncontrolled parameter URLs | Filter links, router behavior, or faceted-navigation rules | Crawl the allowed path and confirm only intended combinations remain discoverable |
| Broken links or redirect chains | Navigation component, shared content block, or link generator | Recrawl the component and confirm direct links to final 200 destinations |
| Bloated sitemap | Sitemap generator, manifest, or CMS export rule | Validate the XML and confirm it contains only canonical, indexable 200 URLs |
Why the fix location matters
A template edit can affect every page that uses it. It therefore needs code access, testing, deployment, and a rollback path. An SEO specialist may diagnose the problem while a developer implements it, or one person may do both. What matters is that the scope names the owner and does not leave the issue as a recurring audit note.
Ask for five things: affected URL pattern, source of the generated output, intended rule, implementation owner, and post-deployment test. That turns a vague recommendation into work that can be shipped and verified.
On a new build, define those shared rules before visual sign-off. The SEO-friendly web design checklist turns navigation, URL states, template fields, mobile parity, schema, and launch validation into an acceptance contract instead of a repair queue.
Fix 1: Templated duplicate titles
The title element helps Google and users understand a page, but Google may generate a different title link in search results. When a template hardcodes the same title across a section, the pages lose a clear description of what makes each one distinct.
If the problem belongs to one important URL, use the ordered on-page SEO audit checklist to test its task, title, content, links, media, and rendered output together. If the same symptom appears across a section, keep reading here and fix the shared generator.
The cause is almost always one template line. A product or service template prints the site name and nothing else, so every page in the section ships identical:
For the wider product and category implementation, use the product and category page SEO guide to connect unique page jobs, crawlable inventory, variants, availability, media, and Product data before fixing individual titles.
The fix is to build the title from the page's own data, so one template produces a unique, descriptive title per page:
To find it yourself, crawl the site with a tool like Screaming Frog and sort by the title column. A block of identical titles is the tell. If you are investigating a title that appears differently in search, compare the rendered title element with a live result for a small sample. Search Console does not provide a title-rewrite report. Titles still matter even when Google generates a different visible title link, so a clear, unique, descriptive title per page remains the right starting point.
Fix 2: The wrong canonical across a whole section
A canonical tag is a strong hint about the preferred URL among duplicate or very similar pages. A wrong value in a shared template can cause Google to choose an unexpected canonical. The classic failure is a section template that points every page at the homepage or one category page.
A distinct indexable page will usually use a self-referencing absolute canonical with the site's preferred protocol, host, and path format. Redirects, internal links, sitemap URLs, and canonical tags should agree on that preferred form.
Check it by viewing source on a handful of pages across each section and reading the canonical line. If two different pages name the same canonical URL, or a page canonicalizes somewhere unexpected, you have found a template bug. This is also the correct tool for consolidating duplicate URLs, which leads straight to the next fix.
Article JSON-LD can repeat the same URL mistake across every guide. The Article schema implementation guide shows how to keep the canonical, author, dates, image, and breadcrumbs aligned with the visible page and validate the rendered output.
If Search Console has already grouped an important URL under this status, follow the complete Crawled - currently not indexed troubleshooting sequence. It checks the stored and live versions, rendered HTML, canonical signals, internal discovery, and whether the page should remain a separate URL.
Fix 3: Parameter URLs splitting the crawl budget
Filters, sorting, and tracking tags generate URLs. A shop with color, size, and sort options can turn one real page into hundreds of near-identical addresses: ?color=red, ?sort=price, ?color=red&sort=price, and so on. Google has a limited budget for how much of a site it will crawl, and on a large or filter-heavy site these parameter URLs can eat it, leaving real pages crawled less often. Crawl budget becomes a real concern once a site runs past roughly ten thousand URLs or leans on faceted navigation. If your site has a few hundred pages and no filters, crawl budget is not your problem right now, so do not lose sleep over it. The canonical part below still applies; the robots.txt blocking matters most once your URL count climbs.
Choose the control based on whether Google needs to crawl the URL. If a parameter version can be crawled, a canonical may help consolidate a genuinely duplicate page:
For filter and sort URLs that should not be crawled, Google documents robots.txt as one option on large faceted sites. Do not combine that assumption carelessly: when robots.txt blocks a URL, Google cannot fetch the page to read its canonical or noindex tag. Test the required facets and keep crawlable any URL that must be discovered or indexed.
Treat the sample as an illustration, not a block to paste blindly. Inventory parameters first, decide which combinations have unique search value, and test the rules on a staging or controlled URL set before deployment.
Fix 4: Broken internal links and redirect chains
Internal links are how Google moves through your site and how ranking signals flow between pages. Two things quietly break that flow. A link to a page that now returns a 404 sends both a crawler and a visitor into a dead end. A link to an old URL that redirects, then redirects again, makes every crawl pay for hops it should not have to.
Neither is fatal on a single link. The damage is structural: these links usually live in shared template parts, a navigation menu, a footer, a sidebar, so one stale URL repeats on every page of the site. The fix is to update the link in the template to point straight at the final, live URL, removing the chain entirely.
A site crawl lists every internal link with its status code. Sort by anything that is not a 200, fix the worst offenders first (the ones in global navigation), and recrawl to confirm the chains are gone.
Fix 5: The bloated sitemap
Your XML sitemap is meant to be a clean list of the pages you want indexed. When it is generated automatically and never pruned, it fills up with URLs that contradict that purpose: pages that redirect, pages that 404, pages marked noindex, pages blocked in robots.txt. Handing Google a list and then telling it half the list should not be indexed sends conflicting signals and wastes the discovery the sitemap exists to help. A good sitemap contains only canonical URLs that return 200 and are meant to be indexed.
A healthy entry lists a live, canonical URL with an honest last-modified date that reflects when the content actually changed:
Search Console's Sitemaps and Page indexing reports will flag much of the rot for you: redirects, 404s, and "excluded by noindex" pages that still sit in the file. The fix is to correct how the sitemap is generated so those URLs never enter it, not to delete rows by hand once a year.
For the full audit sequence, follow the guide to fixing redirects and non-canonical sitemap URLs. It maps each response and canonical state to the right action, then validates the regenerated file in Search Console.
Before a CMS or domain change, put these checks into a migration baseline and post-launch crawl diff. That makes template, redirect, canonical, and sitemap regressions visible while they are still recoverable.
Notice the pattern across all five. Each is one line, one rule, or one template fragment, repeated everywhere. That is why they are worth fixing and why a page-by-page workflow never gets to them. They are properties of the code that builds the site, not of any single page.
What implementation should include
A useful handoff does not stop at "titles are duplicated." It identifies the template or generator, proposes the intended rule, tests representative pages, ships with a rollback path, and recrawls the affected pattern. Finding public-output problems often needs only read access. Fixing them requires authorized access to the CMS, code, or deployment process. For the access boundary, see what access an SEO audit actually needs.
If you use a monthly provider, ask which issues they diagnose, which they implement, and who coordinates the rest. A clear development boundary is acceptable when it is explicit. For common scope patterns, see what a typical SEO retainer actually does, and to confirm whether the release changed visibility, read your own monthly report.
The bottom line
These fixes are template and configuration changes: descriptive titles, coherent canonical signals, deliberate handling of parameter URLs, internal links that point straight at live pages, and a sitemap containing canonical indexable URLs. The durable result comes from changing the generator and verifying the rendered output, not editing affected pages one at a time.
Want to know which of these are live on your site right now? That is what the fixed-price SEO audit finds: a full crawl plus your real Search Console data, with a prioritized fix list you own, and the template-level changes spelled out clearly enough to ship. One report at a flat $150, no retainer, no ranking promises. And if you want these template-level fixes kept up as the site keeps growing, an ongoing SEO retainer does exactly that. Get in touch to start.
Sources checked
Google's title, canonical, crawling, faceted-navigation, and sitemap guidance was rechecked on August 2, 2026.
- Google Search Central: title links and how Google generates them
- Google Search Central: consolidate duplicate URLs (canonicalization)
- Google Crawling Infrastructure: crawl budget guidance for large and frequently updated sites
- Google Search Central: build and submit a sitemap
- Google Crawling Infrastructure: manage crawling of faceted navigation URLs