Same title on more than one page
title_duplicateShort answer
Two or more indexable pages use the identical <title>. In results they look like the same page, and Google may rewrite the titles to tell them apart — or treat the pages as duplicates. Give each page a distinct title; if the pages really are the same, merge them or canonicalise one to the other.
Why it matters
Titles are how both searchers and Google distinguish pages. Duplicates arise from template titles that ignore the page ("Products | Acme" on every category), pagination without page numbers, parameter variants and copied pages. Beyond click-through, duplicate titles are the first symptom of duplicate pages — see Near-duplicate pages.
How Glimana detects it
A site-level rule: Glimana groups indexable 200 pages by exact title and reports every group with two or more members. Each affected page lists the others in its evidence.
How to fix it
- Find the affected pages in Glimana. Open Issues › Same title on more than one page. This is a site-level check, so the single row carries the full evidence: the URLs, values or days involved. The task under Tasks shows the same list and the expected gain.
-
Apply the fix on your platform.
Look at the group. Same content → keep one, 301 or canonical the rest. Different content, lazy template → include the distinguishing field (category name, page number, location). Pagination → "Page 2 of 7" in the title.
Check Search Appearance → Content types templates; make sure archives include
%page%and taxonomy titles use%term_title%.Collections paginated with
?page=2keep the same title; add{% if current_page > 1 %} – Page {{ current_page }}{% endif %}in the title tag.Derive titles from the page's own data; add page numbers to paginated lists.
-
Publish and clear caches. Save and publish, then make sure the crawler will see the new version: WordPress — clear the page cache in your cache plugin and purge the CDN; Shopify — theme and content changes go live on save, but purge any CDN in front of the store; custom code — deploy and purge the edge cache. Check in a private window or with
curl -s https://your-domain/page | grep -i '<title\|canonical\|robots'that the live HTML has changed; Glimana reads what the server sends, not what your browser has cached. - Verify in Glimana. Open the task under Tasks and click Mark as done. The affected pages are queued for a verification crawl within a few hours, and the task closes when the group no longer shares a title. If the check still fails, the task returns to New with a note; when it passes, the task is listed under Resolved technical issues on Impact reports. To check sooner, use Re-crawl affected pages on the issue.
How the fix is verified
The site is re-evaluated after the next crawl; the task closes when the group no longer shares a title.