ScanForge checks in this release

Indexability first

• Page noindex directive
• Missing canonical

Snippet quality

• Missing title tag
• Missing meta description

Crawl stability

• Non-200 page response
• robots.txt not discovered

Missing title tag

The page is missing an HTML <title>, so search results and browser tabs may show weak or rewritten labels.

Why it matters: Title tags are strong relevance and click-through signals. Missing titles reduce snippet quality and make pages look less trustworthy in search results.

First step: Identify indexable templates missing <title> output.

Expected outcome: Cleaner, more consistent search snippets.

Missing meta description

The page has no meta description, so search engines may pull inconsistent body snippets in results.

Why it matters: Meta descriptions do not directly drive rankings, but they heavily influence snippet quality and click-through behavior.

First step: Cover high-traffic landing pages first.

Expected outcome: Stronger snippet consistency across branded and non-branded queries.

Missing H1 heading

The page does not include a primary H1 heading in the rendered content structure.

Why it matters: A missing H1 weakens document hierarchy and makes primary topic intent less clear for users, assistive technologies, and crawlers.

First step: Add one primary H1 near the start of the main content area.

Title too short

The page title is present but too short to communicate clear search intent.

Why it matters: Short titles often miss context that helps users and search engines understand page relevance.

First step: Expand the title with one clear intent phrase and a differentiator.

Title too long

The page title is likely too long and may be truncated in search results.

Why it matters: Truncated titles can hide critical context and reduce click-through confidence.

First step: Trim filler words and keep the primary topic early in the title.

Duplicate title across pages

Multiple URLs share the same title, which can blur topic uniqueness.

Why it matters: Duplicate titles reduce URL-level differentiation and can confuse canonical relevance signals.

First step: Assign unique title patterns per page type and intent.

Meta description too short

The description exists but is too short to communicate a compelling summary.

Why it matters: Short descriptions can under-explain page value in search snippets.

First step: Expand to one clear sentence that reflects user intent.

Meta description too long

The description is likely overlong and prone to truncation in search snippets.

Why it matters: Long descriptions can bury key messaging and reduce snippet clarity.

First step: Trim to a focused sentence with one core benefit.

Missing canonical

The page does not declare a canonical URL.

Why it matters: Missing canonicals can increase duplicate URL ambiguity for indexing systems.

First step: Add a canonical link tag to indexable templates.

Suspicious canonical host mismatch

The canonical target appears to point to a different host than the crawled page.

Why it matters: Cross-host canonicals can accidentally move indexing signals to the wrong domain.

First step: Verify canonical host rules in CMS and template logic.

Page noindex directive

The page exposes noindex via meta robots/googlebot and/or X-Robots-Tag.

Why it matters: Noindex prevents pages from appearing in search results when used on indexable content.

First step: Confirm whether noindex is intentional for the page.

Images missing alt text

One or more images on the page are missing meaningful alt text.

Why it matters: Alt text supports accessibility and gives additional context about important image content.

First step: Add concise alt text to informative images.

robots.txt not discovered

The scan could not fetch /robots.txt with an HTTP 200 response.

Why it matters: Missing robots.txt removes a simple crawl-control and sitemap-discovery mechanism.

First step: Publish /robots.txt on the primary host.

robots sitemap inconsistency

robots.txt has missing or off-host sitemap declarations.

Why it matters: Incorrect sitemap directives can slow URL discovery and indexing consistency.

First step: Declare a canonical same-host sitemap URL in robots.txt.

Multiple H1 headings

The page contains more than one H1, often caused by template or builder component collisions.

Why it matters: Multiple H1 tags are not always fatal, but they can blur primary topic signals and create noisy heading hierarchies.

First step: Keep one page-level H1 and demote additional headline blocks to H2 or H3.

Non-200 page response

A crawled URL returned a redirect or error instead of a clean HTTP 200 response.

Why it matters: Non-200 responses waste crawl budget, break user journeys, and weaken confidence in internal linking quality.

First step: Sort affected URLs by traffic and business importance.

Expected outcome: Cleaner crawl paths and lower error rates.

Blocked cross-host redirect

A crawled URL redirected to a different host, and ScanForge excluded the destination to preserve same-host crawl boundaries.

Why it matters: Cross-host redirects can fragment technical authority and hide destination content from bounded audits.

First step: Standardize canonical host rules for protocol and subdomain variants.

Oversized response body

The HTML response body exceeded crawler safety limits, signaling possible template bloat.

Why it matters: Very large documents can slow delivery, complicate rendering, and reduce crawl efficiency on important pages.

First step: Remove duplicated or unused markup from core templates.

Crawler failure overview

The scan encountered a crawl-blocking failure that can make report data partial or stale.

Why it matters: When crawl coverage is incomplete, prioritization quality drops and unresolved blockers can hide additional issues.

First step: Check uptime, DNS, TLS, and network reachability for the target host.