Colquhoun.AI
← All guides

Research Guides

Check the Head Structure, Not Just the Meta Tag

· Colquhoun.shop editorial

Finding a canonical URL or description somewhere in a page's source does not finish a metadata check. Its surrounding markup matters too. A misplaced integration fragment can make an apparently complete head section unreliable.

This worksheet investigates document structure, not whether a chosen description is persuasive or a canonical target is appropriate. Use it on an authorized site or a local test copy. It is not a claim that Colquhoun.shop performs automated HTML validation.

1. Keep the delivered document as evidence

Choose a representative public page and record its URL, retrieval time and template. Save the HTML response separately from any screenshot or browser-inspected document. Label each artifact so another reviewer knows what was actually inspected.

Write down the expected metadata fields before searching for them. For each field, record its value and location in the document rather than marking “present” as the entire result. Keep uninspected fields unresolved.

2. Inspect the container, not only the field

Google's valid-page-metadata guidance says an invalid element inside the head can cause it to ignore the elements that follow. It names images and iframes as common invalid elements in that location. This is a structural problem, even when the intended metadata text still appears later in the source. Google: Use valid HTML to specify page metadata

Review the sequence around the first suspicious insertion. Identify the component or integration that produced it, the affected template and the fields placed after it. Avoid making an unsupported claim about actual search processing from a source inspection alone.

3. Reduce the issue to a small reproducible case

In a fictional article template, an integration fragment places an image element between the title and the canonical link inside the head. A simple text search finds both metadata fields and reports success. A structure review instead flags the misplaced element and the later metadata for investigation.

The useful bug report includes a short, sanitized excerpt showing the element order, the template name and an example URL. Do not publish private configuration values or full production integration snippets merely to demonstrate the problem. A harmless local fixture can reproduce the placement issue without contacting the integration's service.

4. Fix the producer with its owner

Determine whether the insertion comes from a shared template, content field or service configuration. Check the integration's installation instructions before moving or removing its markup. An SEO repair should not silently disable another team's required workflow.

Make a scoped correction in a test copy and validate the resulting document. Confirm that required metadata values have not changed unintentionally. When the template is shared, include more than the original failing page in the retest.

Moving a troublesome fragment to another position without understanding its purpose is not a complete investigation. Record what the repair changes, who owns the dependency and what behavior must remain intact.

5. Verify the published structure separately from search outcomes

After deployment, retrieve the public page again. Compare the relevant structure with the approved test result and sample other pages using the same component. A clean local file does not prove the public template changed.

Report “the public head structure was corrected and these fields were verified” when that is what the evidence supports. Do not translate a markup repair into a claim that Google has already reprocessed the page or improved its ranking.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.