Head Tag Gaps (retired codes)

0 Intentional Issues

The page conditions for the requested codes that cannot currently produce a finding, kept so they are ready if the codes are reactivated or the crawler input arrives.

Expect zero findings from this page

That is the point of it. The first five codes below are isActive: false in the API issue catalogue, and an inactive code is dropped rather than stored. A fixture that made one of them appear would mean something had changed in the catalogue, not on this page.

The last two are active but unreachable for a different reason each: ssl_certificate_expired needs a host whose certificate has lapsed, and moved_deleted_returnneeds the previous scan's URL list, which the crawler currently passes as an empty array. Both are properties of the environment, not of any page.

#25 link_rel_sitemap
No <link rel="sitemap"> anywhere in the head of this page.
isActive: false. htmlHeadTags.js extracts sitemapLinkUrl but raises nothing. The valid-tag counterpart is /fp-link-rel-sitemap, which declares three correct forms of the tag and must also stay silent.
#20 meta_name_author
No <meta name="author"> on this page.
isActive: false. htmlHeadTags.js extracts authorMetaValue but raises nothing. The valid-tag counterpart is /fp-meta-author.
#22 meta_name_referrer
No <meta name="referrer"> on this page.
isActive: false. htmlHeadTags.js extracts referrerMetaValue but raises nothing. /meta-referrer-gap isolates this same absence on a page where every OTHER head tag is present, so a revived #22 is attributable to one fact; the valid-tag counterpart is /fp-meta-referrer, which also has to keep #70 silent.
#39 search_results_blocked
Internal search IS blocked in /robots.txt — the check's pass condition, already configured.
isActive: false, and the check raises no issue in either direction.
#74 localbusiness_schema_location
/location-schema-gap — location prose (address, telephone, opening hours) with no structured data of any kind, which is what the retired heuristic actually fired on.
isActive: false, and no code path references this issue code at all. A BROKEN LocalBusiness would report as organization_localbusiness_schema (#71) instead, which is why the trigger fixture declares no schema rather than a bad one. The false-positive counterpart is /fp-localbusiness-location: the same prose plus the complete markup the heuristic was guessing about.
#323 ssl_certificate_expired
Not fixturable. The check reads the certificate of the crawled page's own host, and the crawl never leaves this domain.
isActive: true, so it would be stored — but only a site hosted behind an expired certificate can produce it. /http-scheme-audit covers the reachable sibling, #321.
#42 moved_deleted_return
Already present: /status-404 (404), /status-410 (410) and /status-302 (temporary redirect). What is missing is the crawler input, not the pages.
isActive: true, but index.js builds the site context with historicalUrls: [] hard-coded, and the check returns early on an empty list. Nothing on a site can supply a previous scan's URLs. /fp-moved-deleted-return adds the two PASSING states — a 301 to the replacement page, and a legacy-looking URL still served at 200 — and verify-false-positives.mjs calls the detector directly, which is the only way to exercise it at all.

Isolated trigger conditions

The list above puts three head-tag conditions on one document, which is useful as a catalogue and useless as an isolate. Two of the codes have a dedicated page carrying their condition and nothing else, so a revived check is attributable to a single fact:

/meta-referrer-gap — meta_name_referrer (#22). No <meta name="referrer">, and every other head tag present — including a http-equiv referrer policy, so referrer_policy_header (#70) stays silent too.
/location-schema-gap — localbusiness_schema_location (#74). Address, telephone and opening-hours text with no structured data of any kind, which is the prose-only state the retired heuristic fired on.

Both must come back NOT DETECTED. The three site-level codes in the same request — image_sitemap_created, video_sitemap_created and llms_txt_coverage — are live, and their trigger fixtures are /media-library plus the sitemap and llms.txt this deployment serves.

The other half of these codes

Every entry above describes a page with the tag or the markup missing. /false-positive-fixtures covers the opposite condition — the tag present and correct, the schema declared and valid, the retired URL redirecting the way it should — which is the case a revived check is far more likely to get wrong. It also carries the site-level false positives for image_sitemap_created, video_sitemap_created and llms_txt_coverage, which need their own deployment.