Start with the page’s job
Before editing tags, write down what the page lets someone do. A repair guide, a product page, and a working calculator each answer a different need. Metadata should describe that specific experience. A title that promises a calculator belongs on a page with a usable calculator, rather than an article that only talks about one.
Use your browser’s View Source command and inspect the head element. Compare it with the visible heading and main content. Source inspection tells you what was sent initially; developer tools can show changes made later by JavaScript. These are different observations. If a checker cannot execute scripts, an absent tag means absent from the inspected source, rather than absent in every possible rendering.
Write a title and description with a clear promise
Put the distinguishing subject early in the title, then add the useful task or context. For a repair article, “Fix a leaking kitchen tap: washers and seals” is more informative than “Home | Expert solutions | Best services.” Add the brand consistently where it helps recognition, without repeating it several times. Keep the visible H1 aligned with the topic, even when its wording differs.
A description should explain what a visitor will find and any meaningful limitation. For example, “Compare washers and cartridge seals, identify the likely leak source, and follow a shut-off checklist before starting.” This gives a concrete reason to visit. Do not list the same keyword in several variations. There is no universal character count that guarantees an uncut search snippet; display space, query, and device vary.
Review duplicate titles or descriptions at the template level. If every page inherits the homepage wording, fix the page metadata mapping before polishing individual sentences. Search engines can choose a different title or excerpt, so assess the actual content as well as the tags.
<title>Kitchen tap leak diagnosis | Example Workshop</title>
<meta name="description" content="Identify washer and cartridge leaks and prepare safely before a repair.">Separate canonicalization from indexing controls
A canonical link expresses a preferred representative of duplicate or similar content. Use a complete HTTPS URL for the intended page, and make sure it returns the expected content. An accidental homepage canonical on every article can send conflicting signals. Internal links and sitemap entries should consistently use the preferred host and path.
A robots meta noindex directive asks supporting search engines not to index the page. It serves a different purpose from a canonical link. A robots.txt crawl block can prevent a crawler from seeing noindex. For confidential content, use authentication: none of these metadata controls supplies access protection. Inspect HTTP response headers separately because an X-Robots-Tag can apply a directive that an HTML-only report cannot see.
<link rel="canonical" href="https://example.com/repairs/kitchen-tap/">
<meta name="robots" content="index,follow">Check the reading outline
Headings H1 through H6 describe section relationships. Choose a level because of the section’s role, then use CSS for appearance. An H2 can contain several H3 subsections; returning from H3 to H2 starts a peer section. A jump from H2 to H4 deserves review, particularly for people navigating headings with assistive technology.
Do not treat every multiple-H1 observation as an automatic ranking penalty. Inspect whether the page has a clear main topic and a sensible navigable structure. Repeated navigation labels, empty headings, and headings chosen purely for font size are often more actionable than a raw count.
Review text and interface contrast
A useful reading outline also needs legible text. Compare actual foreground/background pairs using relative luminance, rather than averaging RGB values. AA text contrast is at least 4.5:1 for normal text and 3:1 for large text; AAA uses 7:1 and 4.5:1. Large means at least 18pt regular or 14pt bold. Test the actual font size/weight and rendered background, including hover and focus states.
Non-text contrast evaluates meaningful UI boundaries and graphical information against adjacent colors, generally at 3:1 where the criterion applies. A passing two-color calculation does not verify keyboard operation, semantics, images, gradients, transparency or overall WCAG compliance. Retain clear labels and avoid using color alone to distinguish results.
Recheck the exported page
After changing a template, inspect the built HTML of a normal page and an edge case. A correct editor preview does not prove that the deployment emits the same head. Record what you checked and repeat it after a routing or template change.
- One page-specific title and description match visible content.
- The canonical resolves to the intended HTTPS route, using the preferred host.
- Indexing directives are deliberate and crawl access allows them to be seen.
- Social images and URLs are public and relevant.
- The heading outline is useful without its visual styling.
Prepare social sharing independently
Open Graph tags describe a shared object. og:title names the page, og:description summarizes it, og:url identifies its preferred URL, and og:image points to an image the sharing service can request. Use public absolute URLs and review the image’s crop. A 1200 × 630 image is a useful starting canvas for a wide card, but each service can apply its own requirements and cropping.
Twitter/X card metadata can select a card style and provide its own title, description, and image. Keep these values consistent with the page. A local preview approximates appearance; it does not prove that a platform can fetch the image. Check the image response, robots access where relevant, and cached sharing data if an old preview persists. Keep essential text away from image edges and provide useful image descriptions where the platform supports them.
Before publishing the image, inspect the local file's pixel dimensions, aspect ratio and byte size. A size analyzer does not compress the file or promise a smaller encoding at the same quality. Use the intended display area and the sharing platform's actual requirements to choose an image, then measure the final encoded file separately.
Try the Open Graph Preview →