Homepage noindex
A noindexed homepage can remove your strongest authority page from search results and sharply reduce organic lead capture.
Expected outcome: Homepage returns to index eligibility.
Open remediation guideIssue Library
Canonical issue guides for ScanForge reports
Every supported issue type maps to a stable page under /issues so report links, trend items, and fix workflows stay consistent over time.
Use this library as a decision layer: choose your intent, open the issue guide, execute the checklist, and run a fresh scan to confirm movement.
Free vs Pro for ongoing security work
Free includes SEO checks, crawl health, and WordPress security posture visibility. Pro unlocks full WordPress vulnerability intelligence, weekly vulnerability monitoring, and project-level security history.
Start with these high-impact fixes
If your goal is faster organic recovery, tackle these issue guides first and validate with a follow-up scan.
Missing title tag
Pages without a title often lose click-through opportunity because search snippets are rewritten with low-context text.
Expected outcome: Cleaner, more consistent search snippets.
Open remediation guideMissing meta description
When descriptions are missing, search engines choose ad hoc snippets that often under-sell the page value proposition.
Expected outcome: Stronger snippet consistency across branded and non-branded queries.
Open remediation guideNon-200 page response
High-value pages that return redirects or errors dilute crawl efficiency and can suppress revenue-intent landing visibility.
Expected outcome: Cleaner crawl paths and lower error rates.
Open remediation guideKnown vulnerable WordPress component detected
Exposed vulnerable plugin or theme versions can become direct entry points for automated exploitation campaigns.
Expected outcome: Lower exploitability from known component CVEs.
Open remediation guideMissing sitemap discovery
Missing sitemap discovery weakens crawl orchestration and slows index updates for newly published or refreshed pages.
Expected outcome: Faster discovery of newly published URLs.
Open remediation guideTechnical SEO intent
Prioritize crawl reliability, indexability, and snippet quality across non-WordPress and mixed-stack sites.
WordPress-specific intent
Use WordPress-first guides when you need platform-aware checks for indexing drift, hardening, and vulnerability exposure.
Technical checks
Core crawl and on-page issue guides used across all supported sites.
Missing title tag
The page is missing an HTML <title>, so search results and browser tabs may show weak or rewritten labels.
First step: Identify indexable templates missing <title> output.
Open full issue guideMissing meta description
The page has no meta description, so search engines may pull inconsistent body snippets in results.
First step: Cover high-traffic landing pages first.
Open full issue guideMissing H1 heading
The page does not include a primary H1 heading in the rendered content structure.
First step: Add one primary H1 near the start of the main content area.
Open full issue guideTitle too short
The page title is present but too short to communicate clear search intent.
First step: Expand the title with one clear intent phrase and a differentiator.
Open full issue guideTitle too long
The page title is likely too long and may be truncated in search results.
First step: Trim filler words and keep the primary topic early in the title.
Open full issue guideDuplicate title across pages
Multiple URLs share the same title, which can blur topic uniqueness.
First step: Assign unique title patterns per page type and intent.
Open full issue guideMeta description too short
The description exists but is too short to communicate a compelling summary.
First step: Expand to one clear sentence that reflects user intent.
Open full issue guideMeta description too long
The description is likely overlong and prone to truncation in search snippets.
First step: Trim to a focused sentence with one core benefit.
Open full issue guideMissing canonical
The page does not declare a canonical URL.
First step: Add a canonical link tag to indexable templates.
Open full issue guideSuspicious canonical host mismatch
The canonical target appears to point to a different host than the crawled page.
First step: Verify canonical host rules in CMS and template logic.
Open full issue guidePage noindex directive
The page exposes noindex via meta robots/googlebot and/or X-Robots-Tag.
First step: Confirm whether noindex is intentional for the page.
Open full issue guideImages missing alt text
One or more images on the page are missing meaningful alt text.
First step: Add concise alt text to informative images.
Open full issue guiderobots.txt not discovered
The scan could not fetch /robots.txt with an HTTP 200 response.
First step: Publish /robots.txt on the primary host.
Open full issue guiderobots sitemap inconsistency
robots.txt has missing or off-host sitemap declarations.
First step: Declare a canonical same-host sitemap URL in robots.txt.
Open full issue guideMultiple H1 headings
The page contains more than one H1, often caused by template or builder component collisions.
First step: Keep one page-level H1 and demote additional headline blocks to H2 or H3.
Open full issue guideNon-200 page response
A crawled URL returned a redirect or error instead of a clean HTTP 200 response.
First step: Sort affected URLs by traffic and business importance.
Open full issue guideBlocked cross-host redirect
A crawled URL redirected to a different host, and ScanForge excluded the destination to preserve same-host crawl boundaries.
First step: Standardize canonical host rules for protocol and subdomain variants.
Open full issue guideOversized response body
The HTML response body exceeded crawler safety limits, signaling possible template bloat.
First step: Remove duplicated or unused markup from core templates.
Open full issue guideCrawler failure overview
The scan encountered a crawl-blocking failure that can make report data partial or stale.
First step: Check uptime, DNS, TLS, and network reachability for the target host.
Open full issue guideWordPress checks
WordPress context and platform-specific findings surfaced when a footprint is detected.
WordPress footprint context
ScanForge detected common WordPress markers and enabled WordPress-focused checks in the report.
First step: Treat this as platform detection context, not an urgent issue.
Open full issue guideHomepage noindex
The homepage appears to include a noindex directive that can remove your primary URL from search visibility.
First step: Confirm the noindex source in rendered HTML or response headers.
Open full issue guideWordPress security headers incomplete
The homepage is missing or misconfiguring one or more baseline security headers.
First step: Set x-content-type-options to nosniff on homepage responses.
Open full issue guideWordPress HTTPS not enforced
The homepage resolved over HTTP, indicating transport security is not consistently enforced.
First step: Force HTTP-to-HTTPS redirects at the edge or web server layer.
Open full issue guideMissing sitemap discovery
No sitemap was discovered at expected WordPress or common sitemap endpoints.
First step: Validate XML output and response code for the canonical sitemap endpoint.
Open full issue guideXML-RPC reachable
The default XML-RPC endpoint is publicly reachable on the scanned WordPress site.
First step: Disable XML-RPC if no publishing workflow or integration needs it.
Open full issue guidewp-login reachable
The default WordPress login endpoint is reachable and should be hardened.
First step: Enable MFA for administrator and editor accounts.
Open full issue guideKnown vulnerable WordPress component detected
A publicly exposed component version matched a known vulnerable range in ScanForge's local vulnerability watch catalog.
First step: Patch confirmed vulnerable components first by severity and exposure.
Open full issue guidePossible vulnerable WordPress component
A component may match a vulnerable range, but confidence is not high enough for a confirmed finding.
First step: Confirm the exact installed version from WordPress admin or deployment metadata.
Open full issue guide