After publishing, open the article at its URL, preferably in a new window and on a phone. Check that readers see the approved text and can follow the important links. Then get a technical report for that URL.
For example, an editor saved a new guide, but on the site the table extends beyond the phone screen, and a tool link leads to an old page. These are two specific tasks: check the table layout and fix the link address.
Check the Title and the heading in the text
Title is the name set in the page’s meta tag and usually visible in the browser tab. H1 is the main heading inside the article itself. Find both published values and make sure they describe the same piece of content.
If the editor entered “How to check SSL” but the browser tab shows “How to check SSL — Home — reChecker,” ask the developer which template is adding the extra text. In your task, specify the final title you want to see. A length check does not determine whether the title fits the article’s meaning.
For checking individual fields, see the guide to meta tags. After making a change, open the URL again: the value in the editor may differ from the published value.
Follow the links and check the images
Open the links that are part of the instructions or lead to the next action. Check the final URL and whether it matches the page the link text promises. If the article mentions a tool, the link should lead to a route that is actually available, not to an invented name.
For illustrations, check their content, clarity, and relevance to the paragraph. Having a file does not mean it explains the task to the reader. If an image is unavailable or too small, determine whether the file needs to be replaced, the template changed, or the content edited.
The article about broken links describes the technical side of links. Editors also need to check their meaning: a technically successful URL can lead to a different offer or an outdated guide. Record these cases separately from the page response.
Compare the article with another publication
Open an older article with a similar table or the same block. If the problem appears in both, send the developer both URLs and ask them to check the shared style. If only one link is broken, provide its original URL and the expected destination.
On a phone, check lists, tables, captions, and code, if present. For illustrations, check more than just whether the file is there: readers should be able to make out the content and understand which step it relates to. Attach a screenshot and the screen size at which the layout issue appears.
Do not change the article URL just to use a new title without checking existing links. You can often update the text while keeping the existing URL.
Get a report and complete the check
For a new or changed URL, run a technical page check. Check its completion status and date, then select the findings that relate to the approved content. If data was not obtained, record that limitation.
An active paid subscription has no monthly cap on the number of included manual local checks. However, individual batch audits remain subject to the limit of the selected plan. The automatic daily audit of a connected site is limited to one hundred pages and does not replace the acceptance check for each new piece of content at the time of publication.
In the release record, note the results: “example.ru/guide published on 4 October; Title approved; two guide links opened; table readable on a phone; image replaced; technical recheck completed.” Specify any unfinished step, for example, “waiting for the shared style to be fixed.”
In the monitoring dashboard, compare the report date with the publication date. If the site template changes after publication, repeat the check on this article and another piece of the same type. For a content check, ask a colleague to perform one step of the instructions: if they have to guess what to do, clarify the text before marking the task complete.