Webpage SEO Auditor

Inspect title tags, meta descriptions, Open Graph cards, canonicals, and JSON-LD schema.

Meta Tags · Open Graph · JSON-LD

Loading tool workspace...

Overview of the Webpage SEO Auditor

The Webpage SEO Auditor is a real-time on-page technical SEO inspection tool designed for frontend engineers, site reliability teams, digital marketers, and content publishers. By fetching and parsing the raw server-rendered HTML response exactly as search crawlers and social link bots see it, the tool identifies missing, malformed, or suboptimal metadata that can silently hurt search visibility and click-through rates.

Use it as a pre-launch quality gate before shipping new landing pages, verifying international localized routes, troubleshooting broken social preview cards on Slack or X, or auditing editorial blog posts for structured data completeness.

Core Diagnostic Metrics and Inspection Scope

  • Title and Meta Description Analysis: Measures character length, checks keyword alignment between title and summary text, and flags missing or truncated search snippet metadata.
  • Canonical URL and Robots Directives: Verifies whether a clean canonical reference prevents duplicate content dilution and alerts you immediately if noindex or nofollow rules block search indexing.
  • Open Graph and Social Card Preview: Inspects og:title, og:description, og:image, og:url, and Twitter/X Card tags so you can preview how links appear when shared in messaging apps and social feeds.
  • Heading Hierarchy (H1 to H6) and Image Alt Attributes: Checks that the document maintains a single clear H1 primary topic with logical subheading nesting, and scans images for missing alt descriptions affecting accessibility and image search.
  • JSON-LD Structured Data and Editorial Signals: Detects embedded Schema.org JSON-LD entity types (WebApplication, Article, Organization, FAQPage) along with author attribution and publication timestamps.

Step-by-Step Audit Workflow

  1. Enter the full public URL of the target webpage (for example, https://example.com/features) into the address bar at the top of the auditor.
  2. Select the evaluation profile matching your page type—such as a main landing page or an editorial article—and click the audit trigger button.
  3. Review the top-level diagnostic summary counters alongside the live Open Graph social preview card.
  4. Inspect each row of the itemized report to compare extracted HTML values against recommended guidelines, update your markup, and re-run the check to confirm every warning is resolved.

On-Page SEO Best Practices and Security Constraints

  • Verify Server-Side Rendering (SSR/SSG): If your single-page application injects metadata purely via client-side JavaScript after hydration, link preview bots and secondary crawlers may see empty tags. Auditing raw HTTP HTML confirms whether your SSR or pre-rendering pipeline outputs complete head tags on the initial response.
  • Socket-Level SSRF Security Protection: To protect network infrastructure against Server-Side Request Forgery (SSRF) and DNS rebinding, this auditor validates resolved IP addresses directly at the TCP socket layer. Requests targeting localhost (127.0.0.1, ::1), private RFC 1918 subnets (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), link-local cloud metadata endpoints (169.254.169.254), or non-HTTP(S) schemes are blocked automatically.
  • Redirect, Timeout, and Payload Safeguards: The crawler follows up to 3 validated HTTP redirects, enforces a strict 5-second response timeout, and caps decompressed HTML analysis at 2 MB to prevent zip-bomb or stream abuse.
  • Iframe-Isolated Platforms: Closed blogging platforms that wrap content inside cross-frame shells (such as Naver Blog blog.naver.com) or sites gated behind bot-challenge firewalls cannot be audited externally.

Frequently Asked Questions

Can I audit a local development server (localhost) or a staging site on a private VPN?

No. For security reasons, our socket-level SSRF guard blocks all loopback addresses, private intranet IP ranges, and internal hostnames before establishing a network connection. To test an unpublished page, deploy it to a publicly reachable HTTPS preview URL first.

Why does the auditor report missing meta tags when I can see the page title in my browser tab?

This usually happens when a website relies solely on client-side rendering (CSR), meaning the initial HTML document returned by the server contains an empty head section until JavaScript executes in the browser. Switching to server-side rendering (SSR) or static site generation (SSG) ensures crawlers and social preview bots receive complete metadata immediately.

Why did my URL return a fetch error or blocked URL message?

A fetch failure typically occurs if the target server takes longer than 5 seconds to respond, redirects more than 3 times, serves a non-HTML binary file exceeding 2 MB, resolves to a restricted private IP address, or actively blocks automated HTTP user agents via a Web Application Firewall (WAF).

How quickly will changes to my webpage's HTML show up when I re-run the audit?

Immediately, provided your origin server serves the updated HTML. Our auditor fetches live markup on every request without caching stale reports, though if your domain sits behind a CDN cache such as Cloudflare or CloudFront, you may need to purge that edge cache before re-testing.