Trace duplicate metadata to the right template
Admin ·
Suppose a catalogue page has both a useful description and a generic fallback. Find the two declarations in the saved HTML before editing the CMS. The line numbers point to the tags you supplied, so keep the file beside the report if you want to compare the changes.
Follow three findings in the saved catalogue
Open Meta Tags Analyzer. Select Load example and Analyze HTML. There should be nine metadata entries and three findings. Find the duplicate descriptions first, then look at the canonical and robots entries.
The entry on line 5 says Browse the April catalogue & download the price list. The analyzer shows the decoded ampersand. Line 6 says Shop online. In a template that supplies both, keep the specific description and remove the fallback from this page.
| Source lines | Finding | Suggested check |
|---|---|---|
| 5 and 6 | More than one description | Keep the description about the April catalogue. |
| 7 | Relative canonical address | Replace /catalogue/ with https://example.com/catalogue/ in the practice example. |
| 8 | Noindex request | Decide if the page is intended to stay out of search results. |
Google Search Central, supported meta tagsGoogle Search Central, canonical URL signalsGoogle Search Central, robots meta tags and X-Robots-Tag
Verify a focused fix without losing an intentional restriction
Delete the Shop online tag and change the canonical to https://example.com/catalogue/. Analyze the edited source. The report now has eight metadata entries, and the only remaining finding is the noindex request. Its source line has moved up because you removed a line.
If the catalogue remains a preview, keep the restriction and finish checking access separately. If you plan to make the page eligible for search, review both the HTML and any response headers before publishing.
Google Search Central, canonical URL signalsGoogle Search Central, robots meta tags and X-Robots-Tag
Decide whether the saved source answers the question
The report reflects the supplied markup. A copied head can show duplicate fields. A complete document can show when a tag sits outside the head. If a script inserts tags after loading, save the rendered markup and inspect that version separately.
Download JSON to preserve the inspected tags, findings and source lines. Check the file before sharing, since values such as verification tags and draft URLs appear in the results.
Google Search Central, valid page metadataGoogle Search Central, supported meta tags
Common questions
Will the report check that a shared image URL is reachable?
It examines the URL's form from the saved tag. Testing whether the URL returns the right image requires an independent request to the hosted page or image.
Why did I get a parsing diagnostic even though tags were found?
The HTML parser can recover from malformed source, so it can find tags and report an error for the same document. Inspect the identified line and the original markup.
Sources
Put it into practice.
Related guides
- How to Write a Page Head for Search and Sharing
- Write a Meta Description for Narrow Snippets
- Check and Fix Open Graph Tags in HTML
- How to Create and Check FAQPage Markup
- How to Validate Hreflang Return Links
- How to Check Multiple JSON-LD Scripts in HTML
- Resolve Two Links to the Same Journal Map
- Trace a Canonical Conflict in Saved HTML
- Diagnose Robots Meta Tags in Saved HTML
- Repair a Twitter Player Card in Saved HTML