Open the problem page and a similar page of the same type without the error. Compare their fields and additional blocks, then send the pair to a developer. This can help determine whether a specific piece of content needs editing or whether the shared template that creates this type of page needs changing.
Suppose the product name disappears only on cards where an optional field is empty. Filling in that field for one product might hide the symptom, but the template’s handling of empty fields should still be checked.
Describe what you can see on the page
Start with what you actually found. For example, two cards are missing an expected value, or an internal link leads to the wrong address. Saying “the template is broken” is premature: it already offers an explanation that the observation itself does not establish.
Record the exact URLs and date. Specify which pages the audit examined. If some of the section was not crawled, do not automatically extend your conclusion to it. On a connected site, the daily automated audit is limited to 100 pages, while a separate full run has its own selected scope.
Instead of “the template is broken,” write “the title is blank in the tab on /product/2, but appears on /product/1.” The general process for confirming findings is covered in the instructions for verifying audit findings.
Choose a page of the same type
Choose a comparison URL with a similar purpose and structure. For a product card, use another product card; for a service, use a page from the same family. The homepage and a blog post rarely make a useful pair, even if their visual design seems similar.
Check whether the selected page uses an alternative template. The site editor may have a separate design for a promotional card or an older section. Ask the developer whether the pages use the same template.
Choose another product with the same set of fields and record the result. This will make it easier to compare the cards in the next step.
Record differences in the data
| Address | Card data | Resulting title |
|---|---|---|
| /product/1 | Name and variant are filled in | Correct |
| /product/2 | Variant is not filled in | Blank |
| /product/3 | Variant is not filled in | Needs checking |
This is an example comparison to fill in with your own results. Check for other differences too: an additional video, an old block, long text, or a nested category. Do not change several fields at once to get the desired report entry.
If the fields are filled in incorrectly on only one card, agree on an editorial edit. If valid data causes an error on different cards, ask a developer to check the shared rule. The guide to template errors can help you choose additional examples.
Check both pages after the fix
After publishing, check the problem URL and the comparison URL again. The first should show the expected result, and the second should retain the agreed behavior. For a complex template, include a version with an additional block or special content.
Choose a new audit with an appropriate scope, or use a manual method that directly confirms the relevant fact. The absence of a message in the report says little about a URL that was not examined. Review the options for technical checks and the run settings before acceptance.
For a page title, compare the exact published text; for a link, follow it; for an image, open it on the page. The check should address the original finding.
Save the URLs and the date of the result.
In the monitoring dashboard, review subsequent findings, but keep in mind that the daily audit is limited to 100 pages. Two successful cards confirm those variants, not an entire huge catalog. If you need a larger list, choose an appropriate manual scope and specify the unchecked sections separately.