AI SEO Agents use a 10-dimension scoring system to evaluate every article, identifying specific issues and either fixing them automatically or flagging them for review. This page covers the scoring rubric, fix categories, and how the agent prioritizes remediation.
Scoring Rubric
Every article is scored on a 0–100 scale across 10 dimensions. Each dimension contributes a weighted score to the overall total:
| Dimension | Weight | What It Measures |
|---|---|---|
| Word Count | 15% | Total word count. Optimal: 1,500–3,000 words. |
| Keyword Density | 10% | Focus keyword frequency. Target: 0.8–1.2%. |
| Heading Structure | 10% | Proper H1/H2/H3 hierarchy. Exactly 1 H1, 3+ H2s. |
| Meta Quality | 10% | Title (50–60 chars) and description (120–160 chars) with keyword. |
| Readability | 10% | Sentence length, paragraph breaks, transition words. |
| Internal Links | 10% | Links to other pages on the same domain. Minimum 3. |
| Image Usage | 10% | Images with descriptive alt text. Minimum 1 per 500 words. |
| FAQ Presence | 5% | Structured FAQ section with 3+ questions. |
| Introduction Quality | 10% | Opening paragraph hooks reader, includes keyword, sets expectations. |
| Content Depth | 10% | Topic coverage, unique insights, data citations. |

Fix Categories
The audit agent groups every detected issue into one of six fix categories. Each category has its own detection logic, severity thresholds, and remediation strategy. Below is a detailed breakdown of what the agent checks, how it decides what to fix, and what a successful fix looks like.
Broken Links
The audit agent crawls all internal and outbound links using Playwright, checking for 404s, redirect chains (3+ hops), and mixed-content warnings. Broken internal links are fixed automatically by matching the target page's current URL. External broken links are flagged for manual review.
Internal broken links are the most damaging because they waste crawl budget and create dead ends for both users and search engine bots. The agent resolves these by querying your WordPress REST API for the correct current URL of the target page. If the page was moved or its slug was changed, the agent updates the link in-place without altering the surrounding content. For external links, the agent checks the HTTP status code and follows up to 3 redirects. Links that return a 404 or 5xx error are logged with the anchor text, source page URL, and target URL so you can review them in the dashboard.
On a typical 1,000-page site, the agent discovers 15–40 broken internal links per month. Common causes include slug changes after publication, deleted pages that were never redirected, and staging URLs that leaked into production content. The agent also detects mixed-content warnings where an HTTPS page links to an HTTP resource, which can trigger browser security warnings and hurt your Core Web Vitals scores.
Metadata Gaps
Missing or poorly optimized title tags and meta descriptions are the most common SEO issues. The agent checks against these thresholds:
| Element | Optimal | Warning | Error |
|---|---|---|---|
| Title tag | 50–60 characters | > 60 or < 30 | Missing |
| Meta description | 120–160 characters | > 160 or < 70 | Missing |
| URL slug | < 75 characters, hyphens only | Contains underscores | Special characters |
When a title tag is missing, the agent generates one by combining the focus keyword with the article's primary topic, keeping it between 50 and 60 characters. Truncated titles (those cut off by Google at ~60 characters) are rewritten to end on a complete word. For meta descriptions, the agent extracts the most compelling sentence from the introduction, ensures it contains the focus keyword, and trims or expands it to land in the 120–160 character sweet spot. These automated meta fixes alone can increase click-through rates by 15–30% because well-crafted metadata directly influences whether users click your result in the SERP.
URL slugs are checked for length, special characters, and keyword presence. The agent flags slugs that contain underscores (which Google treats as word joiners rather than separators), encoded characters like %20, or unnecessary stop words like "and," "the," or "of." Slug fixes are flagged rather than auto-applied because changing a URL requires a redirect to preserve link equity.
Heading Structure
Proper heading hierarchy is critical for both SEO and accessibility. The agent validates: exactly 1 H1 tag (matching the title), H2 headings for major sections, H3 for subsections, and no skipped levels (e.g., H1 → H3 without H2).
Multiple H1 tags are one of the most common issues on WordPress sites, especially when themes inject the site name or a widget title as an additional H1. The agent detects this by parsing the full DOM (not just post content) and reports the exact element causing the conflict. Skipped heading levels — such as jumping from H2 directly to H4 — confuse screen readers and dilute the topical hierarchy that search engines rely on to understand your content structure.
The agent also checks that at least 3 H2 headings are present (articles with fewer than 3 sections score poorly on content depth) and that heading text is descriptive rather than generic. Headings like "Introduction," "Conclusion," or "More Info" provide no SEO value. The agent flags these and, in optimize mode, rewrites them to include relevant keywords and descriptive phrasing.
Image Optimization
Images without alt text are invisible to search engines. The agent checks every image for: descriptive alt text containing the focus keyword (where natural), proper file naming, lazy loading attributes, and reasonable file sizes. The publishing pipeline automatically sources images using a 3-tier strategy: WordPress media library search → recent uploads → Unsplash stock photography.
Beyond alt text, the agent evaluates image density — you should have at least one image per 500 words to break up text walls and improve engagement metrics. Articles with no images consistently score 8–12 points lower on the overall rubric. The agent also checks for oversized images (files larger than 500 KB) that slow page load times and hurt Core Web Vitals. When the agent detects missing loading="lazy" attributes on below-the-fold images, it flags them for immediate remediation because lazy loading is one of the simplest performance wins available.
For Elementor-published articles, the agent validates that images appear in both the _elementor_data JSON structure and the post_content HTML fallback. This dual-content model is critical because Rank Math reads the HTML fallback, not the Elementor JSON. Missing images in the fallback content can cause Rank Math to report zero images even when the visual page displays them correctly.
Content Quality
Thin content (under 300 words) is flagged automatically. The agent also checks for content freshness — articles that haven't been updated in 6+ months are candidates for enhancement. The optimize mode can automatically rewrite sections to improve depth, add missing subtopics, and boost the overall SEO score to 85+.
Content depth is measured by analyzing topic coverage, the presence of data citations and statistics, the use of examples and case studies, and whether the article addresses common user questions (as identified through SERP "People Also Ask" data). An article that covers a topic superficially — hitting the word count target but lacking substantive detail — will score well on Word Count but poorly on Content Depth. The agent distinguishes between these two dimensions to prevent keyword-stuffed, low-value content from passing quality gates.
Readability is evaluated using average sentence length (target: 15–20 words per sentence), paragraph length (target: 2–4 sentences per paragraph), and the presence of transition words that help readers follow the logical flow. Content that reads like a wall of text with no paragraph breaks will be flagged even if the underlying information is solid.
Schema Markup
The Elementor builder automatically generates FAQ schema (JSON-LD) when your article includes a FAQ section. The audit agent verifies that schema markup is present and valid, checking for required fields and proper nesting.
Valid FAQ schema can earn rich results in Google Search, displaying expandable question-and-answer pairs directly in the SERP. This increases your result's visual footprint and can boost click-through rates by 20–40%. The agent validates that each FAQ item contains both a name (the question) and an acceptedAnswer with text (the answer), and that the JSON-LD is placed in the page <head> or immediately before the closing </body> tag.
The agent also checks for Article schema (@type: Article) with required properties including headline, datePublished, author, and image. Sites that implement both FAQ and Article schema see the strongest rich result performance in competitive SERPs.
The 10-Dimension Scoring System
The scoring system is designed to reflect the factors that actually move rankings, weighted by their real-world impact. Here is a detailed breakdown of what constitutes a good versus bad score for each dimension.
| Dimension | Weight | Full Marks | Failing Score |
|---|---|---|---|
| Word Count | 15% | 1,500–3,000 words of substantive content | Under 1,000 words (scores below 40%) |
| Keyword Density | 10% | 0.8–1.5% with keyword in intro, H2, and meta | Below 0.5% or above 2.0% (over-optimized) |
| Heading Structure | 10% | Exactly 1 H1, 3+ H2s, no skipped levels | Zero H2 headings or multiple H1 tags |
| Meta Quality | 10% | Title 50–60 chars, description 120–160 chars, keyword in both | Missing title or description (scores 0%) |
| Readability | 10% | 15–20 word sentences, 2–4 sentence paragraphs, transition words | Average sentence length over 30 words |
| Internal Links | 10% | 3+ links to live pages with descriptive anchor text | Zero internal links or all links broken |
| Image Usage | 10% | 1 image per 500 words, all with alt text containing keyword | No images or all images missing alt text |
| FAQ Presence | 5% | 3+ questions with 40+ word answers and JSON-LD schema | No FAQ section (receives base 50% score) |
| Introduction Quality | 10% | Keyword in first 100 words, clear hook, sets expectations | No keyword in intro, longer than 150 words before first H2 |
| Content Depth | 10% | Covers all major competitor subtopics, includes data/examples | Surface-level content that restates generic information |
The keyword density dimension deserves special attention because it is the most frequently misunderstood. The target range of 0.8–1.5% means a 2,000-word article targeting "trade show booth cost" should mention that exact phrase or a close variant 16–30 times. The agent checks that keyword placement includes the first 100 words, at least one H2 heading, and the meta description — placement matters as much as frequency.
Before and After: Real Fix Examples
Seeing abstract scoring rules in action helps illustrate what the agent actually does. Here are three concrete examples from real sites managed by AI SEO Agents.
Example 1: Broken Internal Link Fix
A 2,400-word article about trade show logistics contained 5 internal links. After the site owner changed the slug of the "permits and insurance" page from /permits-insurance-logistics/ to /trade-show-permits-insurance/, 3 articles still pointed to the old URL, returning 404 errors. The audit agent detected all 3 broken links in a single crawl, resolved the current URL from the WordPress REST API, and updated each link in-place. The fix was applied within the same audit run — no manual intervention required. The affected articles' Internal Links scores went from 40% to 100%.
Example 2: Missing Meta Description Auto-Generation
A newly published article about CES exhibitor guides had no meta description — the author left it blank, and WordPress did not auto-generate one. The audit agent detected the missing description (Meta Quality score: 20%) and generated one by extracting the most relevant sentence from the introduction: "Plan your CES 2027 exhibit with this comprehensive guide covering booth design, logistics, permits, and budget planning for first-time and returning exhibitors." The generated description was 158 characters, contained the focus keyword "CES exhibitor guide," and ended with a natural call to action. After the fix, Meta Quality jumped to 90%.
Example 3: Heading Hierarchy Correction
An Elementor-built article about custom trade show booths used H3 tags for all section headings because the designer preferred the smaller visual size. This meant the article had zero H2 headings and the heading hierarchy jumped from H1 directly to H3. The audit agent flagged this as a critical heading structure issue (Heading Structure score: 15%). In optimize mode, the agent promoted all section-level H3 tags to H2 and demoted sub-section headings to H3, restoring proper hierarchy. The Heading Structure score improved from 15% to 95%, and the article gained 3 positions in search results within 2 weeks.
Agents fix 500+ issues per month on a typical 1,000-page site. The most common fixes are broken internal links (35%), metadata gaps (30%), and heading structure violations (20%). See how agents deploy 500+ fixes monthly for a detailed breakdown.
Automated Remediation
When the Publisher Agent runs in audit mode, it takes action based on the page score. The agent uses a tiered approach to ensure that high-quality content is left untouched while problematic content is either fixed or pulled from search results to protect your site's overall domain authority.
| Score Range | Action |
|---|---|
| 85–100 | No action needed. Article is performing well. |
| 70–84 | Minor fixes applied (metadata, keyword density adjustments). |
| 50–69 | Metadata fixes applied. Article flagged for content enhancement. |
| Below 50 | Article unpublished (reverted to draft). Enhancement queued automatically. |
Crawl Budget Optimization
Crawl budget refers to the number of pages search engine bots will crawl on your site within a given timeframe. Wasting crawl budget on low-value pages means your most important content may be discovered and indexed more slowly. AI SEO Agents help you optimize crawl budget by identifying and resolving the most common crawl waste issues found on WordPress sites.
- Duplicate content detection: The audit agent identifies pages with substantially similar content, including pagination duplicates, parameter-based variants (e.g.,
?sort=price), and printer-friendly versions. Duplicate pages are flagged with recommendations to canonicalize, noindex, or consolidate. - Orphan page discovery: Pages that have no internal links pointing to them are effectively invisible to crawlers. The audit identifies orphan pages and recommends linking strategies to bring them into your site architecture.
- Thin content consolidation: Pages with fewer than 300 words provide little value to search engines and dilute your crawl budget. The agent flags thin pages and can automatically queue them for content enhancement through the Content Pipeline.
- Redirect chain cleanup: Multiple redirects (3+ hops) waste crawl budget and slow page load times. The audit agent traces redirect chains and recommends direct destination URLs.
- XML sitemap validation: The agent cross-references your sitemap with actual published pages to ensure only indexable, high-value pages are included. Pages returning 404 or 301 status codes are flagged for removal from the sitemap.
Crawl budget optimization is most impactful for large sites with 500+ pages. If your site has fewer than 100 pages, search engines will likely crawl everything regardless. Focus your optimization efforts on content quality and metadata instead.
Core Web Vitals Fixes
Core Web Vitals are Google's metrics for measuring real-world user experience. They directly impact your search rankings, and poor scores can suppress otherwise excellent content. The audit agent measures three Core Web Vitals using Playwright's browser-based rendering and provides specific fix recommendations for each.
| Metric | Good | Needs Improvement | Poor | Common Fixes |
|---|---|---|---|---|
| Largest Contentful Paint (LCP) | < 2.5s | 2.5s – 4.0s | > 4.0s | Optimize hero images, preload critical resources, use CDN |
| Cumulative Layout Shift (CLS) | < 0.1 | 0.1 – 0.25 | > 0.25 | Set explicit image dimensions, avoid dynamic content injection above the fold |
| Interaction to Next Paint (INP) | < 200ms | 200ms – 500ms | > 500ms | Reduce JavaScript execution time, defer non-critical scripts |
The audit agent's content audit action runs a Playwright-based performance assessment that measures TTFB (Time to First Byte), LCP timing, and layout shift events during page load. When TTFB exceeds 2,000ms — a common issue with WordPress sites running heavy plugins — the agent flags it as a high-priority server-side performance issue. Image optimization issues are also detected, including missing lazy loading attributes, oversized image files, and images served without next-gen formats like WebP.
Run a site-wide audit
Trigger the Audit Pipeline from the dashboard or via POST /audit. The audit crawls all published pages and includes performance checks for every page it analyzes.
Review the Core Web Vitals report
The audit report groups pages by CWV status (good, needs improvement, poor). Start with the "poor" group — these pages are actively hurting your search rankings.
Apply recommended fixes
For each flagged page, the report includes specific fix recommendations. Common WordPress fixes include: installing a caching plugin, enabling GZIP compression, optimizing images with ShortPixel or Imagify, and deferring render-blocking JavaScript.
Re-audit to verify improvements
After applying fixes, run another audit to confirm that Core Web Vitals scores have improved. The before-and-after comparison helps you track the impact of each optimization.
Structured Data Repair
Structured data (schema markup) helps search engines understand your content and enables rich results like FAQ dropdowns, breadcrumbs, and how-to cards in search results. AI SEO Agents automatically generate and validate structured data as part of the publishing and audit workflows. The platform supports several schema types that are critical for SEO visibility.
| Schema Type | When Generated | Validation Checks |
|---|---|---|
| FAQ (JSON-LD) | Elementor publish with FAQ section | Valid question/answer pairs, minimum 3 items, no empty fields |
| Article | All published articles | Headline, author, datePublished, dateModified, image present |
| Breadcrumb | Elementor publish with breadcrumbs enabled | Valid itemListElement chain, each item has name and URL |
| Organization | Site-level (not per-article) | Name, URL, logo, sameAs social profiles |
The audit agent validates all structured data on your live pages by parsing the <script type="application/ld+json"> blocks and checking for required fields, proper nesting, and valid JSON syntax. Common issues include missing dateModified fields (which Google uses to determine content freshness), empty author objects, and FAQ schema that references questions not actually present in the visible page content. The agent reports each issue with the specific schema path that needs correction.
FAQ schema is one of the highest-impact structured data types for SEO. When Google renders FAQ rich results, your listing can occupy significantly more SERP real estate. The Elementor builder automatically generates FAQ schema when you include a FAQ section in your article outline, and the Content Agent is trained to include FAQ sections by default.
Redirect Chain Resolution
Redirect chains occur when a URL redirects to another URL that itself redirects again, creating a chain of 2+ hops before reaching the final destination. Each hop adds latency, dilutes link equity, and wastes crawl budget. The audit agent detects redirect chains during the link analysis phase and provides actionable resolution steps.
- 1Detection: The Playwright-based link crawler follows each link through all redirects, recording the full chain (original URL → intermediate hops → final destination). Chains with 3+ hops are flagged as high-priority issues.
- 2Classification: Redirects are categorized by type — 301 (permanent), 302 (temporary), and meta refresh. Mixed redirect types within a single chain are flagged as especially problematic because they send conflicting signals to search engines about whether the redirect is permanent.
- 3Resolution recommendations: For each chain, the agent provides the direct destination URL that should replace all intermediate hops. For internal links under your control, the fix is straightforward: update the href to point directly to the final URL. For inbound links from external sites, the agent recommends updating your server-side redirects to point directly to the destination.
- 4Automated internal link fixes: When the audit agent runs in audit mode with fix permissions, it can automatically update internal links in your WordPress content that point to redirect chains, replacing them with direct links to the final destination URL.
Mobile-First Indexing Compliance
Google uses mobile-first indexing for all websites, meaning the mobile version of your content is what gets indexed and ranked. AI SEO Agents validate mobile readiness as part of the Playwright-based audit, running all checks in a mobile viewport (375px width) to ensure your content is properly accessible and rendered on mobile devices.
- Viewport meta tag: Verifies the presence of
<meta name="viewport" content="width=device-width, initial-scale=1">. Missing viewport tags cause mobile rendering issues that directly impact rankings. - Mobile content parity: Compares the content visible on mobile versus desktop viewports to ensure no critical content is hidden behind desktop-only elements (e.g., tabs, accordions that don't expand on mobile, or CSS
display: noneon mobile breakpoints). - Touch target sizing: Checks that interactive elements (links, buttons, form fields) are at least 48x48 pixels with adequate spacing between them. Small touch targets frustrate mobile users and are flagged in Google's mobile usability report.
- Font size validation: Ensures body text is at least 16px on mobile viewports. Smaller font sizes require pinch-to-zoom, which degrades the mobile experience and can negatively impact rankings.
- Horizontal scroll detection: The agent checks for content that overflows the mobile viewport horizontally, which often indicates unresponsive layout elements like wide tables, code blocks, or images without
max-width: 100%.
Mobile SEO issues are given higher priority weighting in the audit score because they affect all of your rankings, not just mobile-specific queries. A site with excellent desktop content but poor mobile rendering will underperform in search results across all devices. For enterprise sites with complex layouts, consider scheduling weekly audits to catch mobile regressions introduced by theme or plugin updates. See Google Search Console integration for additional mobile usability data directly from Google.
Prioritizing Technical SEO Fixes
Not all technical SEO issues carry equal weight. The audit agent prioritizes fixes using an impact-effort matrix that considers both the potential ranking improvement and the difficulty of implementation. This helps you focus your time and resources on the changes that will move the needle most.
| Priority | Issue Category | Typical Impact | Implementation Effort |
|---|---|---|---|
| Critical | Missing title tags, noindex on important pages, broken canonical tags | High — directly blocks indexing | Low — usually a quick metadata fix |
| High | Core Web Vitals failures, mobile rendering issues, redirect chains | High — affects all page rankings | Medium — may require server/theme changes |
| Medium | Missing meta descriptions, thin content, orphan pages | Moderate — reduces click-through and crawl efficiency | Low to Medium — content updates needed |
| Low | Missing image alt text, suboptimal heading hierarchy, minor schema issues | Low to Moderate — incremental improvements | Low — quick content edits |
The audit report orders findings by priority, so you always know what to fix first. For hands-free remediation, the Publisher Agent's audit mode automatically applies fixes for high-priority issues within its capability (metadata updates, internal link corrections, content quality flags). Server-side issues like TTFB optimization and redirect configuration require manual intervention but are clearly documented with specific action steps in the report. For a broader view of how technical SEO fits into your overall strategy, explore Competitor Analysis and Rank Tracking.
Related Documentation
- AI Agents Deploy 500+ Fixes Monthly — See real data on automated fix volume and impact.
- Connecting Your Site — Set up your WordPress site for automated fixes.
- Rank Tracking — Monitor how fixes impact your search rankings over time.
- Technical SEO Use Case — See how teams use automated fixes at scale.