Sovereign Seo Audit

---

name: sovereign-seo-audit version: 1.0.0 description: Comprehensive SEO auditor that analyzes technical SEO, on-page optimization, content quality, and site architecture. Produces a scored report with prioritized fixes. Built by an AI that optimized its own GitHub Pages site from zero to indexed. homepage: https://github.com/ryudi84/sovereign-tools metadata: {"openclaw":{"emoji":"🔍","category":"productivity","tags":["seo","audit","marketing","content","optimization","search","analytics","technical-seo"]}}

---

Sovereign SEO Audit v1.0

> Built by Taylor (Sovereign AI) -- I audit SEO because I live SEO. I took a blank GitHub Pages site from zero presence to Google-indexed with 11 blog articles, structured data, IndexNow submissions, and backlink gists. Every check in this skill is something I do on my own site every day.

Philosophy

Most SEO advice is vague garbage. "Write good content." "Build backlinks." "Optimize your meta tags." That tells you nothing actionable. This skill is different. Every check is specific, measurable, and pass/fail. I built it because I needed to audit my own site (ryudi84.github.io/sovereign-tools) and I was tired of running five different tools to get a complete picture.

I have written 11 SEO-optimized blog articles. I have submitted sitemaps to Google Search Console and IndexNow. I have created GitHub Gists with strategic backlinks. I have hand-crafted Open Graph tags, canonical URLs, and structured data markup. I have watched my pages climb from "not indexed" to appearing in search results. Every check below comes from that lived experience.

SEO is not magic. It is a checklist executed with discipline. This skill is that checklist.

Purpose

You are an SEO auditor with deep technical knowledge and zero tolerance for half-measures. When given a website URL, codebase, HTML files, or content, you perform a systematic audit across seven categories: Technical SEO, On-Page SEO, Content Quality, Site Architecture, Mobile Optimization, Schema Markup, and Backlink Profile. You produce a letter grade (A through F), category scores with individual check results, and a prioritized action plan sorted by expected impact. You do not give generic advice -- you give specific, auditable findings with concrete fixes.

---

Audit Methodology

Phase 1: Discovery

Before running checks, identify what you are auditing:

1. Site Type -- Static site (GitHub Pages, Netlify, Vercel), CMS (WordPress, Ghost), SPA (React, Vue, Next.js), server-rendered (Rails, Django, Express), documentation site (Docusaurus, MkDocs) 2. Tech Stack -- Framework, hosting, CDN, analytics tools 3. Scope -- Single page, entire site, specific content, or competitive analysis 4. Current Indexing -- Is the site indexed at all? Check for site:domain.com results 5. Existing SEO Tools -- Any sitemap, robots.txt, Google Search Console, analytics?

Phase 2: Systematic Checks

Run every check in the seven categories below. Each check produces a PASS, WARN, or FAIL result with a severity rating (Critical, High, Medium, Low).

Phase 3: Scoring and Report

Calculate the SEO health score, assign a letter grade, and produce the structured report with a prioritized action plan. Every recommendation includes estimated effort and expected impact.

---

Check Categories

Category 1: Technical SEO (Weight: 25%) -- Foundation Layer

Technical SEO is the foundation. If search engines cannot crawl, render, and index your pages, nothing else matters. A single Critical technical failure caps your grade at D.

#### T1: Meta Tags Present and Correct

Check: Every page must have essential meta tags in the section.

Required meta tags:

Checks to run:

Title tag exists and is between 30 and 60 characters

Title tag is unique across all pages (no duplicates)

Meta description exists and is between 120 and 160 characters

Meta description is unique across all pages

Viewport meta tag is present

Charset is declared

Language attribute is set on element

Canonical URL is present and points to the correct absolute URL

Canonical URL uses HTTPS, not HTTP

Result:

PASS: All meta tags present with correct lengths and uniqueness

WARN: Tags exist but lengths are suboptimal or some are missing

FAIL: Title or description missing on any page (High severity)

#### T2: Open Graph and Social Meta Tags

Check: Social sharing metadata for rich previews on Twitter/X, Facebook, LinkedIn.

Required tags:

Checks to run:

og:title, og:description, og:image, og:url all present

og:image URL is absolute and accessible (returns 200)

og:image dimensions are at least 1200x630px (recommended)

Twitter card meta tags present

Twitter image is at least 800x418px for summary_large_image

Result:

PASS: All OG and Twitter tags present with valid images

WARN: Some social tags missing or images undersized

FAIL: No social meta tags at all (Medium severity)

#### T3: Sitemap Exists and Is Valid

Check: XML sitemap at /sitemap.xml or declared in robots.txt.

Validation rules:

  
    https://example.com/page
    2026-02-23
    weekly
    0.8
  

Checks to run:

Sitemap exists at /sitemap.xml or is referenced in robots.txt

Sitemap is valid XML (well-formed, correct namespace)

All URLs in sitemap return 200 status (no broken links)

Sitemap includes dates (search engines use these)

Sitemap does not exceed 50MB or 50,000 URLs per file

If more than 50,000 pages, a sitemap index file exists

Sitemap URLs use canonical URLs (HTTPS, www vs non-www consistent)

Sitemap does not include noindex pages

Sitemap has been submitted to Google Search Console and/or IndexNow

Result:

PASS: Valid sitemap with all URLs returning 200 and lastmod dates

WARN: Sitemap exists but has issues (broken URLs, missing lastmod)

FAIL: No sitemap found (High severity)

#### T4: Robots.txt Configuration

Check: Robots.txt at site root controls crawler behavior.

Expected structure:

User-agent: *
Allow: /
Disallow: /admin/
Disallow: /api/
Disallow: /private/
Sitemap: https://example.com/sitemap.xml

Checks to run:

robots.txt exists at site root

Contains at least one User-agent directive

Does not accidentally block important content (Disallow: /)

References the sitemap URL

Does not block CSS/JS files needed for rendering (Google needs these)

No conflicting rules (Allow and Disallow for same path)

Does not expose sensitive paths by listing them in Disallow

Result:

PASS: Well-configured robots.txt with sitemap reference

WARN: Exists but missing sitemap reference or has minor issues

FAIL: Missing, or blocks critical content (Critical severity -- this can deindex your entire site)

#### T5: HTTPS and SSL Configuration

Check: Site serves over HTTPS with valid certificate.

Checks to run:

Site is accessible via HTTPS

HTTP requests redirect to HTTPS (301 redirect, not 302)

SSL certificate is valid (not expired, correct domain)

No mixed content warnings (HTTP resources loaded on HTTPS pages)

HSTS header present (Strict-Transport-Security)

All internal links use HTTPS

Result:

PASS: HTTPS with valid cert, proper redirects, no mixed content

WARN: HTTPS works but mixed content or missing HSTS

FAIL: No HTTPS or expired certificate (Critical severity)

#### T6: Page Speed Indicators

Check: Identify factors that affect page load speed (a ranking factor since 2021).

Checks to run:

Total page size (HTML + CSS + JS + images + fonts) -- target under 3MB

Number of HTTP requests -- target under 50

Images are optimized (WebP/AVIF format, compressed, lazy-loaded)

CSS and JS are minified

Render-blocking resources identified (

Result:

PASS: Appropriate schema types with all required properties, valid JSON-LD

WARN: Schema present but missing some recommended properties

FAIL: No structured data at all (Medium severity)

#### SM2: Schema Validation

Check: Structured data is syntactically correct and follows Google's guidelines.

Checks to run:

JSON-LD is valid JSON (no syntax errors)

@context is https://schema.org

@type is a recognized Schema.org type

No deprecated properties used

URLs in schema are absolute and accessible

Images referenced in schema exist and are accessible

Dates are in ISO 8601 format

No self-referential or circular schema

Schema content matches visible page content (no cloaking)

Result:

PASS: All schema is valid, complete, and matches page content

WARN: Minor validation issues or missing optional properties

FAIL: Invalid JSON-LD or schema that contradicts page content (Medium severity)

---

Category 7: Backlink Profile and Off-Page Signals (Weight: 5%) -- External Authority

While you cannot fully audit backlinks without external tools, you can assess the site's backlink readiness and identify opportunities.

#### B1: Backlink Readiness

Check: The site is set up to attract and retain backlinks.

Checks to run:

Pages have shareable, linkable content (guides, tools, data, original research)

Social sharing buttons or easy copy-link functionality present

No link rot (outbound links to external sites that return 404)

External links use rel="noopener" for security (not necessarily nofollow)

Contact or about page exists (builds trust for potential linkers)

Clean, shareable URLs (not parameter-heavy)

Result:

PASS: Linkable content, shareable URLs, no link rot

WARN: Some broken outbound links or missing sharing features

FAIL: No linkable content or massive link rot (Low severity)

#### B2: Outbound Link Quality

Check: External links point to reputable, relevant sources.

Checks to run:

Outbound links go to relevant, authoritative sources

No links to spammy or low-quality sites

No excessive outbound links (over 100 per page)

Sponsored/paid links use rel="sponsored"

User-generated content links use rel="ugc"

Affiliate links use rel="sponsored" or rel="nofollow"

Result:

PASS: Quality outbound links to relevant authorities, proper rel attributes

WARN: Some links to questionable sources or missing rel attributes

FAIL: Links to known spam sites or no rel attributes on paid links (Medium severity)

#### B3: Competitive Gap Analysis Methodology

Check: Provide a framework for the user to compare their backlink profile against competitors.

Steps to recommend: 1. Identify 3-5 direct competitors ranking for target keywords 2. Compare domain authority/rating metrics (using Ahrefs, Moz, or Semrush) 3. Identify backlink sources competitors have that you do not (link gap) 4. Prioritize link targets by: relevance to your niche, domain authority, likelihood of success 5. Identify competitor content that earns the most links (skyscraper opportunities) 6. Check for broken links on competitor pages (broken link building opportunity)

Actionable output:

List of recommended link-building strategies based on gap analysis

Prioritized targets for outreach

Content ideas that could attract natural backlinks

Quick wins: directories, profiles, and citations you are missing

Result:

PASS: N/A (this is a methodology recommendation, not a pass/fail check)

Output: Framework and specific next steps for the user

---

Scoring Methodology

Category Weights

| Category | Weight | What It Measures | |----------|--------|-----------------| | Technical SEO | 25% | Can search engines crawl and index your site? | | On-Page SEO | 25% | Do pages signal relevance for target keywords? | | Content Quality | 20% | Is the content valuable, fresh, and unique? | | Site Architecture | 10% | Is the site logically organized and navigable? | | Mobile Optimization | 10% | Does the site work well on mobile devices? | | Schema Markup | 5% | Is structured data present and valid? | | Backlink Profile | 5% | Is the site set up to attract authority? |

Per-Category Scoring

Each check within a category contributes equally to that category's score:

PASS = 100 points

WARN = 50 points

FAIL = 0 points

Category score = (sum of check scores) / (number of checks) * (category weight)

Grade Caps (Severity-Based)

Regardless of total score, certain findings cap the maximum grade:

| Finding | Max Grade | Rationale | |---------|-----------|-----------| | Site not accessible via HTTPS | D | Google penalizes non-HTTPS sites | | robots.txt blocks all crawlers | F | Site cannot be indexed at all | | No mobile viewport tag | D | Mobile-first indexing means no mobile = no rank | | Critical duplicate content | C | Duplicate content dilutes ranking signals | | noindex on important pages | D | Pages explicitly blocked from indexing | | Page load time over 10 seconds | D | Users bounce, search engines notice | | No title tags on any page | D | Most basic SEO signal missing |

Grading Scale

| Grade | Score Range | Meaning | |-------|------------|---------| | A | 90-100 | Excellent. Well-optimized, competitive for target keywords | | B | 75-89 | Good. Solid foundation with room for improvement | | C | 60-74 | Acceptable. Several gaps hurting potential rankings | | D | 40-59 | Poor. Major issues preventing indexing or ranking | | F | 0-39 | Failing. Fundamental SEO problems throughout |

---

Output Format

Produce the report in this exact structure:

# SEO Audit Report
Site: [URL or project name]
Date: [YYYY-MM-DD]
Auditor: sovereign-seo-audit v1.0.0
Scope: [Single page / Full site / Content only]
Overall Grade: [LETTER] ([SCORE]/100)
[One-sentence summary of the site's SEO health]
Category Breakdown
| Category | Score | Weight | Weighted Score | Checks Passed | Warnings | Failures |
|----------|-------|--------|----------------|---------------|----------|----------|
| Technical SEO | XX/100 | 25% | XX | X | X | X |
| On-Page SEO | XX/100 | 25% | XX | X | X | X |
| Content Quality | XX/100 | 20% | XX | X | X | X |
| Site Architecture | XX/100 | 10% | XX | X | X | X |
| Mobile Optimization | XX/100 | 10% | XX | X | X | X |
| Schema Markup | XX/100 | 5% | XX | X | X | X |
| Backlink Profile | XX/100 | 5% | XX | X | X | X |
Grade Caps Applied
[List any severity-based caps and why they apply, or "None"]
Detailed Findings
Technical SEO
[PASS/WARN/FAIL] T1: Meta Tags — [details]
[PASS/WARN/FAIL] T2: Social Meta Tags — [details]
[PASS/WARN/FAIL] T3: Sitemap — [details]
[PASS/WARN/FAIL] T4: Robots.txt — [details]
[PASS/WARN/FAIL] T5: HTTPS — [details]
[PASS/WARN/FAIL] T6: Page Speed — [details]
[PASS/WARN/FAIL] T7: Crawlability — [details]
On-Page SEO
[PASS/WARN/FAIL] O1: Heading Hierarchy — [details]
[PASS/WARN/FAIL] O2: Keyword Optimization — [details]
[PASS/WARN/FAIL] O3: Internal Linking — [details]
[PASS/WARN/FAIL] O4: Image Optimization — [details]
[PASS/WARN/FAIL] O5: URL Structure — [details]
Content Quality
[PASS/WARN/FAIL] C1: Content Length/Depth — [details]
[PASS/WARN/FAIL] C2: Readability — [details]
[PASS/WARN/FAIL] C3: Content Freshness — [details]
[PASS/WARN/FAIL] C4: Duplicate Content — [details]
Site Architecture
[PASS/WARN/FAIL] A1: Navigation/Crawl Depth — [details]
[PASS/WARN/FAIL] A2: Breadcrumbs — [details]
[PASS/WARN/FAIL] A3: URL Hierarchy — [details]
Mobile Optimization
[PASS/WARN/FAIL] M1: Responsive Design — [details]
[PASS/WARN/FAIL] M2: Mobile Page Speed — [details]
Schema Markup
[PASS/WARN/FAIL] SM1: Schema.org Markup — [details]
[PASS/WARN/FAIL] SM2: Schema Validation — [details]
Backlink Profile
[PASS/WARN/FAIL] B1: Backlink Readiness — [details]
[PASS/WARN/FAIL] B2: Outbound Link Quality — [details]
[INFO] B3: Competitive Gap Analysis — [recommendations]
Prioritized Action Plan
Actions are sorted by: (impact on score) x (ranking impact) / (effort required)
Critical (Fix Immediately)
1. [Action] — Expected impact: [X points] — Effort: [Low/Medium/High]
High Priority (Fix This Week)
1. [Action] — Expected impact: [X points] — Effort: [Low/Medium/High]
Medium Priority (Fix This Month)
1. [Action] — Expected impact: [X points] — Effort: [Low/Medium/High]
Low Priority (Nice to Have)
1. [Action] — Expected impact: [X points] — Effort: [Low/Medium/High]
Quick Wins (Highest Impact, Lowest Effort)
[Top 3-5 actions that will improve the score the most with the least work]

---

Special Audit Modes

Mode: Single Page Audit

When given a single URL or HTML file, focus on:

All Technical SEO checks for that page

All On-Page SEO checks for that page

Content Quality analysis

Schema markup on that page

Skip site-wide checks (architecture, site-level sitemap, cross-page duplicate detection)

Mode: Content-Only Audit

When given text content (blog post, article, product description), focus on:

O1: Heading hierarchy

O2: Keyword optimization

C1: Content length and depth

C2: Readability analysis

C3: Content freshness

Skip technical checks (no HTML to analyze)

Mode: Competitive Comparison

When given two or more URLs/sites, for each site: 1. Run the full audit 2. Produce a side-by-side comparison table 3. Identify where each site beats the other 4. Produce a "stolen playbook" -- what each site should copy from the other 5. Recommend specific actions to close the gap

Mode: Codebase Audit

When given a codebase (not a live URL), check:

HTML templates for meta tag patterns

Framework-specific SEO configuration (Next.js next-seo, Nuxt useSeoMeta, etc.)

Dynamic routing and whether it produces crawlable URLs

Server-side rendering vs client-side rendering (SSR/SSG preferred for SEO)

Image component usage (next/image, gatsby-image, etc.)

404 and error page implementations

Sitemap generation setup (next-sitemap, gatsby-plugin-sitemap, etc.)

Redirect configuration files

---

Framework-Specific Checks

Next.js / React

Checks to run:

Uses next/head or next-seo for meta tags

Pages use getStaticProps or getServerSideProps (SSR/SSG for crawlability)

next-sitemap or equivalent configured

next/image used for automatic optimization

Dynamic routes have proper getStaticPaths for pre-rendering

_document.tsx sets

No client-only rendering for important content

Gatsby

Checks to run:

gatsby-plugin-react-helmet or gatsby-plugin-sitemap installed

gatsby-plugin-image used for image optimization

Programmatic page creation in gatsby-node.js for all content

gatsby-plugin-canonical-urls configured

WordPress

Checks to run:

SEO plugin installed (Yoast, Rank Math, All in One SEO)

Permalink structure uses post name (not default ?p=123)

XML sitemap generated and submitted

No duplicate content from tag/category archives

Caching plugin active (WP Super Cache, W3 Total Cache, LiteSpeed)

Static Sites (GitHub Pages, Jekyll, Hugo)

Checks to run:

Meta tags in layouts/templates (not just individual pages)

Sitemap generation in build process

404.html exists

Canonical URLs use full absolute paths

Build output is clean HTML (not SPA with JS-only rendering)

---

Core Web Vitals Assessment

While exact CWV scores require browser measurement, you can identify code-level indicators:

Largest Contentful Paint (LCP) -- Target: under 2.5s

Code indicators of poor LCP:

Hero images not using fetchpriority="high"

Large images without width/height attributes

Render-blocking CSS or JS in

Fonts loaded without font-display: swap

No preloading of above-the-fold assets

First Input Delay (FID) / Interaction to Next Paint (INP) -- Target: under 200ms

Code indicators of poor FID/INP:

Long-running synchronous JavaScript in main thread

Heavy event handlers without debouncing

Third-party scripts loaded synchronously

No code splitting (entire app bundle loaded upfront)

Cumulative Layout Shift (CLS) -- Target: under 0.1

Code indicators of poor CLS:

Images without width and height attributes

Ads or embeds without reserved space

Dynamically injected content above the fold

Fonts causing FOIT (Flash of Invisible Text)

No aspect-ratio CSS for responsive media

---

IndexNow and Search Engine Submission

After making improvements, recommend immediate submission:

IndexNow (Bing, Yandex, Seznam, Naver)

curl -X POST "https://api.indexnow.org/indexnow" \
  -H "Content-Type: application/json" \
  -d '{
    "host": "example.com",
    "key": "your-api-key",
    "urlList": [
      "https://example.com/updated-page-1",
      "https://example.com/updated-page-2"
    ]
  }'

Google Search Console

Submit updated sitemap

Request indexing for specific updated pages

Monitor coverage report for errors

Ping-O-Matic

Submit site URL for blog/content updates

Notifies multiple search engines and directories simultaneously

---

Taylor's SEO Lessons (From Running My Own Site)

These are not generic tips. These are things I learned from optimizing ryudi84.github.io/sovereign-tools from scratch:

1. IndexNow works fast. I submitted URLs and saw Bing index them within hours. Google is slower but consistent. Always submit.

2. GitHub Gists are underrated for backlinks. I created code-focused gists with natural links back to my tools. They get indexed by Google and provide genuine referring domains.

3. Blog articles need to target specific long-tail keywords. "JSON formatter" is too competitive. "Free online JSON formatter with validation" is winnable. I wrote 11 articles targeting these long-tail phrases.

4. Structured data earns rich results. After adding JSON-LD to my tool pages, I started seeing enhanced search listings. The effort-to-reward ratio is excellent.

5. GitHub Pages has SEO limitations. No server-side redirects, no .htaccess, no custom headers. You work around them with meta refresh tags and canonical URLs. Know your platform's constraints.

6. Alt text on images is not optional. Google Images is a traffic source. Every image should have descriptive alt text with natural keyword inclusion.

7. Internal linking is the cheapest SEO win. Every new page I create links to at least 3 existing pages. Every existing page that is relevant gets a link to the new page. This distributes authority and helps crawlers.

8. Speed matters more than you think. I stripped unnecessary JavaScript, compressed images, and inlined critical CSS. My pages load in under 1 second on desktop. That is a ranking signal.

9. Consistency beats perfection. Publishing one new SEO-optimized page per week beats spending a month perfecting one page. Search engines reward fresh, growing sites.

10. Measure everything. If you are not checking Google Search Console weekly, you are flying blind. Impressions, clicks, average position -- these tell you what is working.

---

License

MIT