Technical SEO & AEO Fix Checklist — Wisedocs.ai

Prepared for: Wisedocs Date: 2026-03-09 Scope: 414 indexed pages, 100 deeply audited Current Scores: Technical SEO 42/100 | AEO Readiness 65/100

This is an actionable, prioritized checklist for fixing every technical SEO and AEO issue identified on wisedocs.ai. Each item includes the exact fix, affected pages, estimated effort, and expected impact. Items are ordered by impact-to-effort ratio.

Priority 1 — Homepage H1 Tag (30 minutes)

Severity: CRITICAL | Impact: High | Pages affected: 1

The homepage (wisedocs.ai/) has no H1 tag. The first heading element on the page is an H2. This suppresses keyword relevance for every head term Wisedocs should rank for on the highest-authority page on the site.

Webflow implementation: Edit the Homepage hero section. Change the headline element from its current tag (likely a div with styled text or an H2) to an H1. One field change in the Webflow designer.

Priority 2 — Render-Blocking Scripts (1-2 week sprint)

Severity: CRITICAL | Impact: High | Pages affected: All 414

Every page loads an average of 33 JavaScript files, with 8-10 render-blocking scripts in <head>. Average inline JavaScript per page: 23,043 bytes. This directly suppresses Core Web Vitals (LCP, FID, INP).

Webflow implementation: Most script loading can be controlled in Webflow's Project Settings > Custom Code section. Third-party scripts (analytics, chat widgets, tracking pixels) should use defer. Webflow's native scripts cannot be deferred but are already optimized. Image format conversion is available in Webflow's asset manager (enable WebP auto-conversion).

Priority 3 — Structured Data Implementation (1 week)

Severity: CRITICAL | Impact: High | Pages affected: 99 of 100 audited pages have zero schema

Only 1 page has any structured data, and that schema is malformed. This makes Wisedocs invisible to rich results, AI Overviews, and knowledge graph extraction.

Article Schema (blog posts)

Template JSON-LD for blog posts:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "{{Blog Post Title}}",
  "author": {
    "@type": "Person",
    "name": "{{Author Name}}"
  },
  "datePublished": "{{Publish Date}}",
  "dateModified": "{{Last Modified Date}}",
  "image": "{{Featured Image URL}}",
  "publisher": {
    "@type": "Organization",
    "name": "Wisedocs",
    "logo": {
      "@type": "ImageObject",
      "url": "https://wisedocs.ai/logo.png"
    }
  }
}

FAQPage Schema

Template JSON-LD for FAQ pages:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Question text here",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Answer text here"
      }
    }
  ]
}

BreadcrumbList Schema

Organization Schema Fix

Speakable Schema

Priority 4 — Title Tags and Meta Descriptions (2-3 days)

Severity: HIGH | Impact: CTR improvement | Pages affected: 63 titles, 66 descriptions

Titles exceeding 60 characters (63 pages)

Descriptions exceeding 160 characters (66 pages)

Priority 5 — Image Alt Text (1 week)

Severity: HIGH | Impact: Accessibility + image search + AI parsing | Pages affected: All 100 audited

657 images are missing alt text across the audited pages. This is both an accessibility compliance issue and an SEO signal loss.

Priority 6 — Broken Links and Mixed Content (1 day)

Severity: CRITICAL (security) | Impact: Trust + crawl health | Pages affected: 41 source pages

Broken internal link (1)

Mixed content (3 pages)

Broken external links (60 across 41 pages)

Priority 7 — Multiple H1 Tags on Blog Posts (1-2 days)

Severity: WARNING | Impact: Topical signal dilution | Pages affected: 25 blog posts

25 blog posts have 2-7 H1 tags. This is a Webflow CMS template issue where section headings are styled as H1 instead of H2/H3.

Priority 8 — Publication Dates on All Content (1 day)

Severity: HIGH | Impact: AEO freshness scoring | Pages affected: All content pages (0% currently show dates)

Zero audited pages show visible publication dates. AI answer engines deprioritize content they cannot date.

Priority 9 — Open Graph and Twitter Card Tags (2-4 hours)

Severity: MEDIUM | Impact: Social sharing quality | Pages affected: All 414

100% of pages are missing og:url and all Twitter Card meta tags.

Priority 10 — llms.txt Optimization (2-4 hours)

Severity: MEDIUM | Impact: AEO discoverability | Pages affected: 1 file

The current llms.txt exists (ahead of most competitors) but is missing key elements and is excessively long at ~117K tokens.

Priority 11 — Content Structure for AI Parsing (ongoing)

Severity: MEDIUM | Impact: AEO citation eligibility | Pages affected: 90% of content pages

90% of pages lack lists, tables, or summary blocks — all formats that AI answer engines prefer to extract and cite.

Scoring Targets

Completing Priorities 1-8 should move the scores to:

Category Current Target (after fixes)
Technical SEO 42/100 70-75/100
AEO Readiness 65/100 80-85/100
On-Page SEO 48/100 75-80/100
Structured Data 12/100 70-80/100
Page Speed Signals 25/100 55-65/100
Citation Optimization 35/100 60-70/100

Timeline

Sprint Items Duration Dependencies
Week 1 Priority 1 (H1), Priority 6 (broken links), Priority 8 (dates), Priority 9 (OG tags), Priority 10 (llms.txt) 2-3 days None — all independent
Week 2 Priority 4 (titles/descriptions), Priority 7 (H1 duplicates) 3-4 days None
Week 3-4 Priority 2 (render-blocking JS), Priority 5 (alt text) 7-10 days May need dev support for JS audit
Week 3-4 Priority 3 (structured data) 5-7 days Parallel with above
Ongoing Priority 11 (content structure) Continuous Editorial process change

Total estimated timeline: 4-6 weeks for Priorities 1-10. Priority 11 is an ongoing editorial standard.

◇

How This Was Made

AI-native workflows let one person do what agencies need teams for. The AI does the heavy lifting. The human makes every judgment call.