🔍 AgentsBooks.com — Full Website Audit Report
Date: May 5, 2026 | Audited by: Claude Agent Audit Engine
🟡 TOTAL WEBSITE SCORE: 61 / 100
| Pillar | Score | Grade |
|---|---|---|
| 🔎 SEO | 36/100 | ❌ Needs Urgent Work |
| ⚡ Performance | 70/100 | 🟡 Good Foundation |
| 🔒 Security | 80/100 | ✅ Strong |
| 📝 Content & Links | 50/100 | 🟠 Developing |
| 🎨 Design & UX | 68/100 | 🟡 Solid |
SECTION 1 — PLAIN ENGLISH OVERVIEW
"What's actually going on with your website?"
The Good News First 🎉
AgentsBooks has a genuinely impressive product and the bones of a great marketing website. You've got Cloudflare protecting and speeding up your site, your pages load quickly, your security setup would make most startups jealous, and your content team is producing real, useful articles. The product story is compelling and clearly written. Users who land on the homepage understand what you do almost immediately — that's harder than it sounds.
You've also done something most early-stage companies skip: you've already thought about the full marketing funnel — comparison pages, use-case pages, integrations, guides, personality agents. That strategic thinking is visible and valuable.
The Not-So-Good News 😬
Here's where things get honest.
Your #1 problem: about 50 pages on your website are broken. They return a blank "page not found" error. The tricky part? Google already knows about all of them — because you've listed every single one in your sitemap.xml (the file that tells Google "here's everything on our website"). So Google's crawlers show up at your comparison pages, your use-case pages, your guides section, and your personality-agent pages... and find nothing. This is actively hurting your ability to rank in search. It's like handing out business cards that link to a closed shop.
The sections that are currently broken (every page in them):
- 🔴 All 16 use-case pages (
/use-cases/...) - 🔴 All 6 competitor comparison pages (
/compare/vs-...) - 🔴 All 12 personality-agent pages (
/personality-agents/...) - 🔴 All 14 guide/documentation pages (
/guides/...) - 🔴 The main
/guidespage itself
That's roughly 49 out of 133 URLs in your sitemap — 37% — silently failing.
Your #2 problem: Google can't read your page summaries. Every search result you've ever seen shows a title and a short description below it. That description comes from something called a "meta description." On AgentsBooks, none of your pages have one. Not the homepage, not the pricing page, not blog posts, not features — nothing. This means Google is guessing what to show, which almost always looks worse and gets fewer clicks.
Your #3 problem: no schema markup anywhere. Schema markup is special code you add to your pages that tells Google "this is a review," or "this is a FAQ," or "this is an article by James Torres published on February 15." Google rewards this with richer search results — star ratings, FAQs that expand right in Google, author names, and more. AgentsBooks has zero of it. Your competitors who do have it are getting more real estate in search results for free.
How Did This Happen?
This is actually very common for fast-moving startups. You planned a full content architecture (comparison pages, use-cases, guides — all smart ideas) and listed them in the sitemap before building them, or those pages existed and got removed without updating the sitemap. The security and infrastructure work was clearly done thoughtfully. The SEO fundamentals just haven't caught up yet.
The good news: these are all fixable in days, not months. The strategic thinking is already there.
SECTION 2 — WHAT TO FIX AND IN WHAT ORDER
"Your prioritized action plan in plain English"
🚨 Fix These First (This Week)
1. Remove broken URLs from your sitemap
Your sitemap is sending Google to 49 pages that don't exist. Until those pages are built, remove them from sitemap.xml. This stops the bleeding immediately. If you have a deployment pipeline, this is a 15-minute job.
2. Write meta descriptions for your top 10 pages Start with: homepage, pricing, the 6 feature pages, and 2-3 blog posts. Each one is 1–2 sentences (under 160 characters). This directly affects how your site looks in Google search results and how many people click through.
3. Set up canonical tags sitewide A canonical tag is a small line of code that tells Google "this is the main version of this page, don't confuse it with anything else." Add them to every page. Most CMS platforms can do this automatically.
🟠 Fix These Next (This Month)
4. Build or redirect the broken pages
The comparison pages (vs-Zapier, vs-LangChain, etc.) are SEO gold — people Googling "AgentsBooks vs Zapier" are ready to buy. Same for use-case pages. Build them or redirect them to working alternatives.
5. Add Article schema to all blog posts This tells Google your blog posts are real articles, who wrote them, and when. It can unlock "rich results" in Google — author names, publish dates, and higher perceived credibility.
6. Add FAQ schema to your FAQ sections Several pages already have FAQ sections. Adding 5 lines of code turns them into expandable Google search results. Free visibility boost.
🟡 Fix These This Quarter
7. Turn on Cloudflare page caching Your CDN (Cloudflare) is running in pass-through mode — it's not actually caching your HTML pages. Enabling caching means faster loads for everyone and less load on your server.
8. Add alt text to your product images Images with no descriptions are invisible to Google Image Search and to visually impaired users. This is an accessibility requirement (WCAG AA standard) and an SEO opportunity.
9. Tighten your Content Security Policy
Your site uses unsafe-inline in its security settings — it works, but it's slightly less secure than ideal. A security-minded enterprise buyer reviewing your compliance page might notice. Worth cleaning up.
10. Build more content 16 blog posts is a start, but it's thin for a company trying to own the "AI agent platform" category. Double it to 32 over the next 60 days, focused on long-tail keywords your comparison and use-case pages would have captured.
SECTION 3 — TECHNICAL DEEP DIVES
🔎 SEO AUDIT — Score: 36/100
Indexability & Crawlability
| Check | Status | Notes |
|---|---|---|
| robots.txt | ✅ Pass | Well-structured; public pages allowed, auth/API blocked; AI bots explicitly invited (GPTBot, ClaudeBot, PerplexityBot) — smart forward-thinking move |
| Sitemap.xml | ⚠️ Critical Issue | Exists at /sitemap.xml, contains 133 URLs with priority weights, but ~49 URLs (37%) return HTTP 404 |
| HTTP→HTTPS redirect | ✅ Pass | http://agentsbooks.com → https://agentsbooks.com/ via 301 |
| www→non-www redirect | ✅ Pass | https://www.agentsbooks.com → https://agentsbooks.com/ via 301 |
| HEAD method support | ⚠️ Minor | Server returns 405 Method Not Allowed for HEAD requests (returns Allow: GET). Not a crawler blocker but non-standard |
| Canonical tags | ❌ Not Confirmed | Not detected on any page sampled. Without canonicals, duplicate content risk exists (e.g., URL parameters, trailing slashes) |
Broken Sitemap URLs by Section
| Section | URLs in Sitemap | Status |
|---|---|---|
| Use-Case Pages | 16 | 🔴 All 404 |
| Personality & Team Agents | 12 | 🔴 All 404 |
| Comparison Pages | 6 | 🔴 All 404 |
| Guide Pages (inc. /guides) | 15 | 🔴 All 404 |
| Blog Articles | 16 | ✅ All Live |
| Feature Pages | 6 | ✅ All Live |
| Integration Pages | 5 | ✅ All Live |
| Core Pages | 6/7 | ✅ 6 Live, /guides 404 |
Impact: Google Search Console will log these as soft 404 errors. Any PageRank that flows to these URLs is wasted. Sitemap credibility is damaged.
Titles, Meta Descriptions & Heading Structure
Title Tags — Present but Issues Exist
| Page | Title | Length | Issue |
|---|---|---|---|
| Homepage | AgentsBooks — The Operating System for AI-Native Service Companies | 65 chars | ✅ Good |
| Blog index | 📝 AgentsBooks Blog | 20 chars | ❌ Too short; emoji in title |
| Blog post | How to Build Your First AI Agent in Under 3 Minutes | AgentsBooks — AgentsBooks Blog | 86 chars | ⚠️ Over 60 chars; "AgentsBooks" repeated twice |
| Pricing | Pricing — AgentsBooks | AI Agent Builder Plans | 47 chars | ✅ Good |
| About | About AgentsBooks — The OS for AI-Native Service Companies | 58 chars | ✅ Good |
| Features | Inferred from H1; not confirmed distinct | — | ⚠️ Unconfirmed |
Meta Descriptions — Universally Missing ❌
Zero confirmed meta descriptions across all pages sampled (homepage, pricing, about, blog index, 3 blog posts, 3 feature pages, contact). Google will auto-generate snippets from page text — typically resulting in lower CTR vs. crafted descriptions.
Recommended meta description formula:
[Core value prop] + [specific benefit] + [soft CTA]. Max 155 characters.
Example (homepage): "Build and deploy autonomous AI agents for your service business — no code needed. Join 1,000+ builders running on AgentsBooks. Start free today."
H1/H2 Structure Analysis
| Page | H1 | Issue |
|---|---|---|
| Homepage | "Run an AI-Native Service Company." | ✅ Strong, keyword-rich |
| Blog index | "📝 AgentsBooks Blog" | ⚠️ Emoji in H1; screen-reader friction |
| Pricing | "💰 Simple, Transparent Pricing" | ⚠️ Emoji in H1 |
| About | "The Operating System for AI-Native Service Companies" | ⚠️ Duplicates homepage H1/title |
| Blog posts | Match article title | ✅ Correct |
| Feature pages | Match feature name (e.g., "🧠 Agent Brain") | ⚠️ Emojis in H1 |
- Multiple H2s per page ✅
- H2 hierarchy is logical and keyword-relevant ✅
- Emoji usage in headings: cosmetically fine but can confuse screen readers and appears inconsistently
About page H1 duplicates homepage H1 — this signals potential duplicate content to Google.
Schema.org / Structured Data
❌ No structured data detected on any page.
| Schema Type | Applicable Pages | Status | Missed Opportunity |
|---|---|---|---|
Organization | Homepage, About | ❌ Missing | Google Knowledge Panel eligibility |
WebSite with SearchAction | Homepage | ❌ Missing | Sitelinks search box in Google |
Article / BlogPosting | All 16 blog posts | ❌ Missing | Rich results: author, date, breadcrumbs |
FAQPage | Pricing, Blog posts, Features | ❌ Missing | Expandable FAQs in search results |
BreadcrumbList | Blog posts (breadcrumbs exist visually) | ❌ Missing | Breadcrumb trails in SERPs |
SoftwareApplication | Homepage, Features | ❌ Missing | App rating / category signals |
PriceSpecification | Pricing page | ❌ Missing | Rich pricing signals |
⚡ PERFORMANCE AUDIT — Score: 70/100
Core Web Vitals & TTFB (Measured)
| Metric | Measured Value | Target | Status |
|---|---|---|---|
| TTFB (Homepage) | 148ms | < 800ms | ✅ Excellent |
| TTFB (Blog) | 176ms | < 800ms | ✅ Excellent |
| TTFB (Pricing) | 144ms | < 800ms | ✅ Excellent |
| LCP | Not directly measurable (no browser render) | < 2.5s | ⚠️ Requires field data |
| INP | Not directly measurable | < 200ms | ⚠️ Requires field data |
| CLS | Not directly measurable | < 0.1 | ⚠️ Requires field data |
Note on CWV: TTFB being sub-150ms is an excellent foundation. Real CWV scores require Chrome User Experience Report (CrUX) data or Lighthouse lab testing. The fast TTFB means LCP-from-server is not a bottleneck.
Page Weight
| Page | HTML Size | Assessment |
|---|---|---|
| Homepage | 108 KB | ✅ Reasonable for content density |
| Blog index | 89 KB | ✅ Good |
| Pricing | 86 KB | ✅ Good |
HTML payload is clean. Total page weight including JS/CSS/images not measurable without browser tool, but HTML alone is well-optimized.
Infrastructure & Caching
| Check | Status | Notes |
|---|---|---|
| CDN | ✅ Cloudflare | Confirmed via server: cloudflare header |
| HTTP/2 | ✅ Active | Confirmed via HTTP/2 in curl response |
| GZIP/Brotli compression | ✅ Assumed Cloudflare default | No content-encoding in sampled headers (Cloudflare compresses transparently) |
| HTML page caching | ⚠️ Not active | cf-cache-status: DYNAMIC — every page request hits origin. Enabling Cloudflare page caching rules for public pages would cut TTFB for cached visitors to ~5ms |
| Static asset caching | ✅ Assumed via Cloudflare | Standard Cloudflare behaviour for CSS/JS/images |
| Server timing | ✅ Present | server-timing: total;dur=2.1 — origin processes requests in ~2ms. Excellent |
Render-Blocking & JS/CSS Observations
From the CSP header, the following third-party scripts are loaded:
- Google Tag Manager ⚠️ (render-blocking if not deferred)
- Microsoft Clarity ⚠️ (analytics/heatmap — adds JS weight)
- Facebook Connect ⚠️ (FB pixel)
- Reddit Pixel ⚠️
- Google Ads / DoubleClick ⚠️ (multiple domains)
- Cloudflare Insights ✅ (lightweight)
- DataTables + jsDelivr CDN ⚠️ (DataTables is 85KB+ — only load on pages that need it)
- Instagram embed scripts ⚠️
Concern: 5–6 third-party tracking/ad scripts loading simultaneously can significantly delay INP and LCP, especially on mobile. These should be loaded asynchronously, deferred, or triggered only after user consent (which your cookie banner provides — confirm JS actually defers until consent is given).
🔒 SECURITY AUDIT — Score: 80/100
HTTPS / TLS
| Check | Status | Notes |
|---|---|---|
| HTTPS enforced | ✅ Pass | HTTP 301 → HTTPS sitewide |
| HSTS header | ✅ Strong | max-age=63072000 (2 years), includeSubDomains, preload — best practice |
| TLS version | ✅ Cloudflare default | TLS 1.2/1.3 enforced by Cloudflare |
| Mixed content | ✅ Likely clean | CSP img-src and connect-src restrict to HTTPS origins |
Security Headers
| Header | Value | Status | Notes |
|---|---|---|---|
Strict-Transport-Security | max-age=63072000; includeSubDomains; preload | ✅ Excellent | HSTS preload list eligible |
X-Frame-Options | SAMEORIGIN | ✅ Pass | Clickjacking protection active |
X-Content-Type-Options | nosniff | ✅ Pass | MIME-sniffing blocked |
Referrer-Policy | strict-origin-when-cross-origin | ✅ Pass | Good balance of privacy and functionality |
Permissions-Policy | camera=(), microphone=(), geolocation=() | ✅ Pass | Sensitive APIs locked down |
Cross-Origin-Opener-Policy | same-origin-allow-popups | ✅ Pass | OAuth flows work; cross-origin isolation partial |
Content-Security-Policy | Present and detailed | ⚠️ Partially | See breakdown below |
Cross-Origin-Embedder-Policy | Not present | ⚠️ Missing | Low-priority for SaaS apps |
Content Security Policy Deep Dive
Your CSP is impressively comprehensive — rare for a startup. However:
script-src 'self' 'unsafe-inline' ...
style-src 'self' 'unsafe-inline' ...
'unsafe-inline'for scripts allows any inline<script>tag to run. This partially defeats XSS protection that CSP is designed to provide.- Fix: Replace
'unsafe-inline'withnonce-basedorhash-baseddirectives. Requires app-level changes to generate per-request nonces. - The CSP script-src whitelist has 40+ Google country domains (
.google.co.uk,.google.de, etc.) — this is very permissive and increases attack surface slightly. Consider consolidating using*.google.comor the canonical ad domain list.
Exposed Sensitive Files
| File | HTTP Status | Status |
|---|---|---|
/.env | 404 | ✅ Protected |
/.git/config | 404 | ✅ Protected |
/wp-admin | 404 | ✅ Not WordPress (as expected) |
Cookie Security
- Cookie consent banner present ✅
- Consent state stored in
localStorage— not in a cookie, so noHttpOnly/Secure/SameSiteflags to check for consent itself - Recommendation: Verify that actual session/auth cookies (set at
/login) useSecure,HttpOnly, andSameSite=StrictorLaxflags. These weren't directly observable without a live login, but Auth0 (referenced inimg-src cdn.auth0.com) typically sets these correctly by default.
📝 CONTENT & LINKS AUDIT — Score: 50/100
Content Inventory & Quality
| Content Type | Count | Avg. Length | Quality Signal |
|---|---|---|---|
| Blog posts | 16 | ~1,100–1,400 words | ✅ Solid depth, real authors with bios |
| Feature pages | 6 | ~450–800 words | ⚠️ Thin — some under 500 words |
| Integration pages | 5 | Unknown | ⚠️ Not audited in depth |
| Use-case pages | 16 planned | — | ❌ All 404 |
| Comparison pages | 6 planned | — | ❌ All 404 |
| Guides/Docs | 14 planned | — | ❌ All 404 |
| Personality agents | 12 planned | — | ❌ All 404 |
Content strengths:
- Named authors with real bios (James Torres, Sofia Petrova, Alex Rivera, Tomer Ofer) — strong E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) signals ✅
- Breadcrumb navigation implemented visually ✅
- FAQ sections in blog posts ✅
- External citations (McKinsey, Gartner, Anthropic, Stack Overflow) in articles ✅
- Clear category taxonomy (Getting Started, Tutorial, Deep Dive, Strategy, Industry) ✅
- Social share buttons on articles ✅
Content weaknesses:
- Zero meta descriptions — the most universally missing element
- Feature pages are thin (450–800 words) for pages targeting competitive keywords
- 16 blog articles is modest for a company targeting "AI agent" keyword category
- Blog H1 uses emoji:
"📝 AgentsBooks Blog"— minor but affects text-only parsers - About page H1 mirrors homepage H1 word-for-word — duplicate content signal
Keyword Coverage Analysis
| Target Keyword Cluster | Coverage | Notes |
|---|---|---|
| "AI agent platform" | ✅ Homepage H1, multiple mentions | Core term well-covered |
| "AI agents vs chatbots" | ✅ Blog article | Good informational capture |
| "build AI agent" | ✅ Blog article + features | Solid |
| "AI agent for [vertical]" | ❌ Use-case pages all 404 | Major gap |
| "AgentsBooks vs [competitor]" | ❌ Comparison pages all 404 | High-intent keyword gap |
| "AI agent documentation" | ❌ Guides all 404 | Navigational/trust gap |
| "AI sales agent", "AI support agent" | ❌ Use-case pages 404 | Lost commercial traffic |
| "no-code AI agent builder" | ✅ Blog mentions | Could be stronger on homepage |
Internal Linking
- Blog posts link to features, pricing, and other articles ✅
- Navigation links all core sections ✅
- "Continue Reading" and "Related Articles" sections in blog posts ✅
- Orphan pages: None detected among live pages — but the 49 broken pages in the sitemap may have had orphan risk anyway
- Missing: Feature pages don't cross-link to relevant use-case pages (which are 404 anyway)
Backlink & Authority Signals
(Note: External backlink profile requires tools like Ahrefs/Majestic not available in this audit)
Observed trust/authority signals:
- Product Hunt listing (linked from About) — good early signal ✅
- Discord community (1,000+ members) — social proof ✅
- GitHub presence linked ✅
- LinkedIn + X profiles linked ✅
- Customer testimonials with named roles and companies ✅
- Powered by Google Cloud, Anthropic, OpenAI, Stripe — brand association ✅
- Zero inbound editorial backlinks visible from page content
Recommendation: The comparison pages (vs-Zapier, vs-LangChain, etc.) are high-intent pages that attract natural backlinks from communities comparing tools. Building these is the fastest path to acquiring links organically.
🎨 DESIGN & UX AUDIT — Score: 68/100
Responsive Design
| Breakpoint | Status | Notes |
|---|---|---|
| Mobile | ✅ Likely responsive | Cloudflare + modern framework; viewport meta present |
| Tablet | ✅ Likely responsive | No issues indicated in content structure |
| Desktop | ✅ Confirmed | Content renders cleanly at full width |
Direct breakpoint testing requires a browser rendering environment. Site architecture (Cloudflare, modern JS, viewport meta) strongly suggests full responsiveness.
Accessibility (WCAG AA)
| Check | Status | Notes |
|---|---|---|
| Skip to content link | ✅ Present | Confirmed on contact page and login page |
| Form labels associated | ✅ Pass | Contact form labels properly associated with inputs |
| Required field marking | ✅ Pass | * used consistently on all required fields |
| Cookie consent | ✅ Present | Reject/Accept options available |
| Alt text — product/hero images | ❌ Missing | Product screenshots and hero images have no confirmed alt text |
| Alt text — blog playbook images | ❌ Missing | "Build a Student-Tutor Agent" playbook image lacks alt text |
| Emoji in headings | ⚠️ Partial | Screen readers read emoji descriptions aloud ("brain emoji Agent Brain") — may sound awkward but functional |
| Colour contrast | ⚠️ Unverified | Requires visual rendering — dark text on white/light background visually appears sufficient |
| Focus states | ⚠️ Unverified | Requires interactive browser testing |
| Tap targets (mobile) | ⚠️ Unverified | Navigation and CTAs appear standard-sized |
Navigation & Information Architecture
What works:
- Top-level nav is well-structured: Product → Solutions → Resources ✅
- Dropdown menus cover all major sections ✅
- Footer has clear column structure (Product / Resources / Legal) ✅
- Legal pages (ToS, Privacy, Cookies, DMCA, AUP) all present ✅
- Multiple CTAs at each decision point ✅
What needs attention:
- Navigation links to
/guidesand/use-cases/...pages that are all 404 ❌ - Solutions menu items (Content & Social, Sales & Leads, Customer Support, DevOps & Engineering, Multi-Agent Teams) likely link to broken
/use-cases/pages ❌ - Users clicking these nav items hit dead pages — direct harm to conversion and trust
CTA & Conversion Funnel
| CTA | Placement | Quality |
|---|---|---|
| "Start Free" | Homepage hero, pricing, features | ✅ Clear, repeated, action-oriented |
| "Book a Demo" | Nav, multiple pages | ✅ Secondary conversion path |
| "Browse Templates" | Homepage | ✅ Low-friction discovery path |
| Newsletter signup | Blog sidebar, About, Homepage | ✅ Lead capture present |
| "Start 3-Day Free Trial" | Pricing page | ✅ Reduces commitment friction |
| Agent builder prompt | Homepage | ✅ Interactive, high engagement signal |
Funnel observation: The conversion funnel is well-designed for bottom-of-funnel (start free, book demo, trial). The middle-of-funnel is broken — the use-case pages and comparison pages that would capture "AI agent for marketing" or "AgentsBooks vs Zapier" searches and walk users toward a decision are all 404.
Forms
| Form | Status | Notes |
|---|---|---|
| Contact form | ✅ Good | 4 required fields, subject dropdown, clear submit |
| Newsletter signup | ✅ Good | Single email field, low friction |
| Cookie consent | ✅ Good | Reject/Accept both available (GDPR-compliant intent) |
| Agent builder prompt | ✅ Good | Innovative first-party product demo within homepage |
PRIORITIZED MASTER FIX LIST
🔴 Priority 1 — Do This Week (High Impact, Low Effort)
| # | Fix | Pillar | Est. Effort |
|---|---|---|---|
| 1 | Remove all 49 broken URLs from sitemap.xml until pages are built | SEO | 1 hour |
| 2 | Write and deploy meta descriptions for top 10 pages | SEO | 2–3 hours |
| 3 | Add canonical <link rel="canonical"> tags to every page | SEO | 1 day (template-level change) |
| 4 | Fix or redirect navigation links pointing to 404 pages | UX | 2 hours |
🟠 Priority 2 — Do This Month (High Impact, Medium Effort)
| # | Fix | Pillar | Est. Effort |
|---|---|---|---|
| 5 | Build the 6 comparison pages (vs-Zapier, vs-LangChain, etc.) | SEO + Content | 1–2 weeks |
| 6 | Build the use-case pages (start with top 5 by search volume) | SEO + Content | 2–3 weeks |
| 7 | Add Article + BreadcrumbList schema to all blog posts | SEO | 1 day |
| 8 | Add FAQPage schema to pricing and feature pages | SEO | 1 day |
| 9 | Add Organization + WebSite schema to homepage | SEO | 2 hours |
| 10 | Add alt text to all images sitewide | Accessibility | 1–2 days |
🟡 Priority 3 — Do This Quarter (Medium Impact, Variable Effort)
| # | Fix | Pillar | Est. Effort |
|---|---|---|---|
| 11 | Enable Cloudflare HTML page caching for public pages | Performance | 1–2 hours |
| 12 | Defer/lazy-load third-party scripts (FB, Reddit, Clarity) until after consent | Performance | 1 day |
| 13 | Replace 'unsafe-inline' in CSP with nonce-based approach | Security | 1–2 days |
| 14 | Fix double "AgentsBooks" in blog post title tags | SEO | 1 hour |
| 15 | Expand blog to 32+ articles focused on use-case keywords | Content | 4–6 weeks |
| 16 | Build /guides documentation section | Content + SEO | 2–4 weeks |
| 17 | Expand feature pages to 1,000+ words with use cases and examples | Content | 1 week |
| 18 | Verify audit/session cookie flags (Secure, HttpOnly, SameSite) | Security | 2 hours |
| 19 | Run Lighthouse on mobile to get real CWV scores | Performance | 1 hour |
| 20 | Remove duplicate H1 on About page (mirrors homepage) | SEO | 15 min |
STRATEGIC OBSERVATIONS
Where AgentsBooks stands right now: You've built an excellent technical and product foundation. The infrastructure is fast, secure, and professional. The product story is clear. But search discovery is almost entirely blocked — the 49 broken pages represent the exact content types that capture commercial-intent searchers (comparison shoppers, vertical-specific searches, how-to-get-started searches). You're leaving Google traffic on the table at the moment you need it most.
The biggest untapped opportunity: The comparison pages. Someone Googling "AgentsBooks vs LangChain" or "best AI agent platform vs CrewAI" is 80% of the way to buying. These pages build both SEO rankings and backlinks from communities where developers discuss tooling. They should be the first content investment after fixing the 404s.
The second biggest opportunity: Schema markup. Adding Article, FAQ, Organization, and WebSite schema takes one developer less than one sprint and can immediately unlock rich results in Google — visually more prominent, higher CTR, zero additional content needed.
Topical authority path: With 16 good blog posts already live, you're one editorial push away from owning "AI agent operations" as a topic cluster. The framework (tutorials, case studies, industry takes, deep dives) is already there. The volume just needs to double.
Audit conducted May 5, 2026. Data collected via live HTTP inspection, header analysis, sitemap crawl, and multi-page content sampling across 25+ URLs.