WordPress SEO Health Checker

1. Title Tag & Meta Description Optimization

A meta title and description are what most searchers actually see in results before clicking — a well-written pair is directly responsible for a page's click-through rate, independent of its ranking position. As covered in Google's SEO Starter Guide, titles should be unique per page and front-load the most important, specific words (avoiding generic titles duplicated across many pages), and descriptions work best when they accurately preview the page's actual content rather than being keyword-stuffed. WordPress SEO plugins generate these automatically from a template — always review the generated output rather than assuming the default template fits every page type well.

2. Managing Canonical URLs in WordPress

WordPress generates several accessible URL variants for the same piece of content by default — with and without a trailing slash, via `?p=123` shortlinks, and (on paginated archives) across `/page/2/`, `/page/3/`, etc. A correctly self-referencing canonical tag on each page tells search engines which one variant to treat as authoritative, consolidating ranking signals rather than splitting them. Once your canonical tags are confirmed correct, verify your sitemap only lists those canonical URLs (not the variants) with the WordPress XML Sitemap Validator.

3. Implementing Open Graph & Schema JSON-LD

Open Graph tags (og:title, og:description, og:image) control how a page appears when shared on social platforms and in chat previews — without them, shared links often fall back to an unpredictable auto-generated preview. Schema.org JSON-LD structured data is separate and serves search engines specifically, enabling rich-result eligibility (reviews, FAQs, breadcrumbs, products) depending on content type. Both are typically generated by an SEO plugin, but coverage varies by page template — confirm indexability isn't accidentally blocked with the WordPress robots.txt Checker alongside checking these tags are present.

4. Crawl Efficiency via Nimbica Static Edge

Nimbica pre-renders cacheable pages into static HTML served from edge locations, giving crawlers fast, consistent responses. This helps crawl budget go further on larger sites, but it's a delivery-layer improvement — it doesn't generate, validate, or fix the metadata itself, which is why the checks in this tool (and the SEO plugin generating that metadata) remain necessary regardless of hosting or caching architecture.

5. How to Use This Audit

1. Scan a representative page of each template type on your site (homepage, a blog post, a product/service page, a category archive) rather than assuming one scan represents the whole site.
2. For any missing element, check your SEO plugin's settings for that specific content type — templates are often configured per post type.
3. Confirm the meta title and description read naturally and accurately describe the page — a passing "present" check doesn't mean the content is well-written.
4. Re-scan after making changes to confirm they took effect, especially if page caching is active.

6. Common Mistakes

• Using the same title/description template with no per-page customization. Auto-generated titles that are identical in structure across hundreds of pages waste an opportunity to differentiate each page's actual value in search results.
• Multiple H1 tags on one page. Some themes and page builders render more than one H1 (often a hero-section heading plus a duplicate SEO-plugin-inserted one) — a single, clear H1 per page remains the accessibility and SEO best practice.
• Auto-generated Open Graph images that don't represent the content. A generic site-wide fallback image on every shared link is a missed opportunity compared to a content-specific image or auto-generated preview card.

7. Limitations

This tool checks presence, not quality — it confirms a meta title, canonical tag, Open Graph tags, or schema markup exist, but doesn't grade whether the title is compelling, the description accurately summarizes the content, or the schema's data is factually correct. It also audits exactly one URL per scan; a full site audit means checking a representative sample across each page template, not a single page.