The Librarian SEO Audit
Your site barely shows up on Google for the searches your audience is running. Here's what's broken — and the 44k+ monthly searches you could rank for instead.
Start here · top 5 fixes
See the full list →What's wrong, why it matters, and how to fix it.
7 structural issues.
Read full assessment
thelibrarian.io is a 63-page site with near-zero organic visibility outside its own brand name. Of 28 ranked keywords, 99.1% of traffic value ($7,249 of $7,315) comes from "the librarian" at position 8 — a query Google primarily interprets as the TV/movie franchise, not a SaaS product. The site's actual organic competitors are IMDB and Apple TV, not AI assistant tools. The entire /articles/ section (26 URLs) is product-focused walkthroughs that target no search queries, and 41% of the sitemap consists of press releases and newsletters that serve no SEO function. No page carries structured data.
The product itself has clear differentiation: WhatsApp-native AI assistant for email, calendar, and file retrieval across Google Workspace is a genuinely specific wedge. The site has some content strengths — articles are substantive (600-1,800 words), feature real use cases, and cover a range of verticals (real estate, insurance, sales). The foundation for topical authority exists; it just hasn't been pointed at discoverable keywords. With the right competitive set corrected and 10-15 keyword-targeted articles, this domain could move from invisible to competitive in the "ai personal assistant" cluster within 3-6 months.
01Brand name collision with entertainment IP is stealing 99% of branded search
"The librarian" (110,000 vol/mo) is dominated by the TV/movie franchise. The site ranks #8 for its own brand name, behind IMDB, Apple TV, and Fandom. The top 3 organic "competitors" by keyword intersection are IMDB (12 kw), Apple (11 kw), and ALA.org (10 kw) — none are SaaS competitors; they rank for entertainment and library-science queries. Google interprets nearly every query containing "librarian" as entertainment or profession intent. This means the site's entire branded search funnel leaks to IMDB and streaming platforms. Of 28 total ranked keywords, the branded term accounts for $7,249 of $7,315 total traffic value (99.1%).
Show more
The site has near-zero non-branded organic visibility. Every piece of content that leans on the brand name in titles and headings reinforces Google's confusion about the domain's topical identity.
4 evidence points
- ·"the librarian" — pos 8, vol 110,000/mo, but top organic competitors are IMDB (12 kw intersection), Apple (11 kw), ALA.org (10 kw)
- ·Branded term accounts for $7,249 of $7,315 total etv (99.1%)
- ·Self-named competitors listed as fandom.com, ala.org, wordpress.com — all entertainment/library sites, zero SaaS overlap
- ·Only 28 total ranked keywords, 5 on page 1
The fix
1. Add SoftwareApplication and Organization schema to the homepage to signal SaaS entity type to Google.
2. Shift page titles from "The Librarian - [feature]" to keyword-led titles like "AI Email Assistant for Busy Founders | The Librarian".
3. Build a branded Knowledge Panel claim via Google's entity verification to disambiguate from the entertainment IP.
4. Prioritize non-branded keyword targeting ("ai personal assistant", "ai email assistant") to build topical authority independent of the collision.
02Zero SEO-targeted content — all 26 articles are product walkthroughs with no keyword strategy
Every /articles/ page is a product feature demo or thought-leadership post. None target discoverable search terms like "ai personal assistant" (pipeline pillar), "ai email assistant", or "how to manage email overload." The content reads as sales collateral: "Get debriefed for all business meetings," "Share Files & Pics with The Librarian," "The Perfect Sales Companion." These solve no search query a prospect would type. The keyword pipeline found 24 pillar and 6 audience opportunities but 0 competitor keywords — because the site has published nothing in the competitive keyword space.
Show more
With only 28 ranked keywords total, the site is invisible for every non-branded term that would drive trial signups.
4 evidence points
- ·26 /articles/ URLs — all product walkthroughs or thought leadership, zero keyword-targeted
- ·Keyword pipeline: 24 pillar + 6 audience + 0 competitor opportunities
- ·Example titles: "Gemini Nano Banana - A New Era for Image Generation," "No More Excuses - Effortless Social Media in 2025" — no search intent alignment
- ·Only 1 non-branded keyword on page 1: "librarian ai" pos 2, vol 260/mo
The fix
1. Publish 8-10 how-to guides targeting pipeline pillars: "ai personal assistant," "ai email assistant," "motion alternative."
2. Build comparison pages ("Lindy AI vs The Librarian," "Motion alternative for email") to capture bottom-funnel intent.
3. Repurpose existing feature walkthroughs as internal-link targets from new SEO content, not as standalone discovery pages.
4. Add FAQ schema to each new article to compete for AI Overview and featured snippet slots.
0341% of sitemap is press releases and newsletters — thin content diluting domain authority
15 /press_releases/ + 11 /newsletters/ = 26 URLs, representing 41% of the 63-URL sitemap. Press releases are typically boilerplate and newsletters are repurposed email content — neither serves search intent. For a domain with only 28 ranked keywords, every indexed URL that doesn't earn clicks drags the domain's perceived quality. Google's helpful content system evaluates site-wide quality signals; a small site where nearly half the pages are non-search content sends a clear "not built for searchers" signal. These pages consume crawl budget that should be spent on the product and (future) editorial pages.
3 evidence points
- ·Sitemap: /press_releases/ — 15 URLs, /newsletters/ — 11 URLs (26 of 63 total = 41%)
- ·Only 28 total ranked keywords across the entire domain
- ·63 indexed URLs but near-zero non-branded organic traffic
The fix
1. Noindex all /press_releases/ and /newsletters/ pages via meta robots tag.
2. Remove them from the XML sitemap.
3. Keep the pages live for PR/investor linking but block them from organic index.
4. Redirect any press release that has earned external backlinks to the most relevant /articles/ page via 301.
04Title tags waste 17+ characters on brand prefix, reinforcing entity confusion
Every fetched page title starts with "The Librarian - " (17 characters). One title hits 121 characters. On a domain fighting brand-name collision with an entertainment franchise, leading every title with the ambiguous brand name actively reinforces Google's misclassification. The descriptive keyword content gets pushed past the ~60-character SERP truncation point. For example, "The Librarian - Create multiple events in seconds with the best Calendar AI" (75 chars) truncates before the keyword-rich portion. The uniform prefix also creates near-duplicate title patterns across 36+ pages, reducing SERP click differentiation.
3 evidence points
- ·All 36 fetched pages use "The Librarian - [text]" prefix pattern
- ·One title hits 121 characters: "The Librarian - The New Year Resolution Every Founder Needs..."
- ·Title at 75 chars truncates: "The Librarian - Create multiple events in seconds with the best Calendar AI"
The fix
1. Move brand name to the end of all title tags: "[Primary Keyword] | The Librarian."
2. Cap titles at 60 characters to prevent SERP truncation.
3. Front-load the target keyword in every title.
4. For the homepage, use "AI Personal Assistant for Email & Calendar | The Librarian" to establish SaaS intent.
05Zero structured data across entire site
0 of 36 fetched pages have any schema markup (all show schema: N). No Organization, SoftwareApplication, Article, FAQ, or BreadcrumbList schema detected anywhere. For a SaaS product competing in the AI assistant space, SoftwareApplication schema is the primary signal that tells Google "this is software, not a TV show." The absence compounds the brand-name collision: without entity-level schema, Google has no structured signal to disambiguate thelibrarian.io from the entertainment franchise. Missing Article schema on /articles/ pages also forfeits rich result eligibility.
3 evidence points
- ·0 of 36 fetched pages have schema markup (schema: N on every page)
- ·No SoftwareApplication schema to signal SaaS identity to Google
- ·Brand confusion with entertainment IP would benefit most from entity-disambiguating schema
The fix
1. Add Organization schema to the homepage with name, url, logo, and sameAs links to social profiles.
2. Add SoftwareApplication schema with applicationCategory: "BusinessApplication", operatingSystem, offers (freemium + Pro pricing).
3. Add Article schema to every /articles/ page with author, datePublished, dateModified.
4. Add FAQ schema to any page with Q&A content.
5. Add BreadcrumbList schema site-wide.
06Most article pages lack real H2 structure — footer nav elements are the only detected headings
At least 10 of the 36 fetched pages show only "Company," "Solutions," and "Legal" as H2s — these are footer/nav elements, not content headings. Pages like "Must-Have AI Tools for Startup Founders in 2025" (1,238 words) and "How Insurance Agents win back their days" (1,276 words) have zero content H2s visible to the parser. Without semantic heading structure, Google cannot identify subtopics within these pages, reducing their eligibility for passage ranking and featured snippets. Long-form content without H2 subheadings also fails the readability bar for helpful content assessment.
4 evidence points
- ·10+ pages show only footer labels ("Company", "Solutions", "Legal") as H2s
- ·"Must-Have AI Tools for Startup Founders in 2025" — 1,238 words, zero content H2s
- ·"How Insurance Agents win back their days" — 1,276 words, zero content H2s
- ·"ChatGPT vs WhatsApp AI assistants" — 1,562 words, zero content H2s
The fix
1. Audit every /articles/ page and ensure content sections use proper H2/H3 heading hierarchy.
2. Move footer navigation out of H2 tags into a semantically appropriate element (nav with spans or divs).
3. Include target keywords or related terms in content H2s for passage-ranking eligibility.
4. Aim for one H2 per 200-300 words of content.
07Competitive intelligence is blind — self-named competitors are entertainment and library sites
The business lists fandom.com, ala.org, and wordpress.com as competitors. These are entertainment wiki, library association, and blogging platform sites — none compete in the AI assistant SaaS space. The keyword pipeline produced 0 competitor-layer keywords because it had no real competitors to mine. Actual competitors like Lindy AI, Motion, Reclaim.ai, and Clara Labs rank for hundreds of "ai assistant" and "ai scheduler" terms the site doesn't touch. Without correct competitive targeting, the keyword pipeline cannot identify gap terms or comparison-page opportunities that drive high-intent bottom-funnel traffic.
3 evidence points
- ·Self-named competitors: fandom.com, ala.org, wordpress.com — zero SaaS overlap
- ·Keyword pipeline: 0 competitor-layer keywords generated
- ·Organic competitor intersection dominated by IMDB and Apple — entertainment entities
The fix
1. Reconfigure the competitive set to: Lindy AI, Motion, Reclaim.ai, Clara Labs, Clockwise.
2. Re-run the keyword pipeline with corrected competitors to generate competitor-layer opportunities.
3. Prioritize "[competitor] alternative" and "[competitor] vs" pages as first SEO content.
4. Use competitor domains in DataForSEO intersection analysis to find high-volume terms they rank for that thelibrarian.io doesn't.
What you currently rank for.
TOP 10 RANKED KEYWORDS · BY VOLUME
30 keywords to win. 10 articles to write.
Highest-leverage first. Keywords with a ready article on top.
The keyword opportunities cluster around three pillars The Librarian should own: AI personal assistant (the broadest, ~19,000 combined monthly searches across variants), AI email assistant (~3,500 combined), and competitor alternatives (Motion, Lindy AI, ~500 combined but zero-competition). The site currently has 26 blog-style articles, but none target these commercial keywords. Instead, they cover feature announcements and thought leadership that don't match any search query with measurable volume. The content exists but doesn't connect to what people actually search for.
SHOW SUGGESTED ARTICLE
SHOW SUGGESTED ARTICLE
SHOW SUGGESTED ARTICLE
SHOW SUGGESTED ARTICLE
SHOW SUGGESTED ARTICLE
On-page issues across your top pages.
- Title tag too long3 pages
Over 65 characters. Google truncates titles past ~60-65 chars.
thelibrarian.io/articles/create-multiple-events-in-seconds-with-the-best-calendar-aithelibrarian.io/articles/gemini-nano-banana-a-new-era-for-image-generationthelibrarian.io/articles/the-new-year-resolution-every-founder-needs-win-back-time-with-an-ai-assistant-for-your-small-business - Title tag too short3 pages
Under 30 characters. Likely missing keyword context.
thelibrarian.io/about_usthelibrarian.io/press_releasethelibrarian.io/security - Meta description too short3 pages
Under 120 characters. Wasting SERP real estate.
thelibrarian.io/about_usthelibrarian.io/insurancethelibrarian.io/grievance-redress-policy - Schema markup missing3 pages
No structured data found — missing rich-result eligibility (Article, FAQ, Product, etc.).
thelibrarian.io/articles/get-debriefed-for-all-business-meetingsthelibrarian.io/articles/the-librarian-remembers-all-the-important-detailsthelibrarian.io/articles/get-debriefed-every-morning-with-morning-briefs
SITE PROFILE
- Name
- The Librarian
- Audiences
- Startup founders and executives managing busy schedules · Marketing consultants and professionals drowning in email · Small teams using Google Workspace and Slack
- Locale
- EN / US
- Sitemap pages
- 36
Who's ranking for the same searches.
Want us to fix these for thelibrarian?
One keyword in, one published article out, every day. We'll ship against the 30-keyword list above.
The autopilot. $99/mo.
- Specialist AI agents for audits, research, keywords, and articles
- Live SERP keyword data, scored on real intent
- Fact-checked drafts with citations on every claim
- Quality gate refuses thin or unfounded copy
- Native publish to WordPress, Webflow, Shopify, Wix, Ghost
- Schema, internal links, sitemap pings baked in
Beyond the autopilot.
- Site consolidation + redirect plans
- CMS migrations between platforms
- Geo expansion + multi-region strategy
- Custom integrations + webhooks
- White-glove publishing for enterprise teams
REAL DATA ABOVE · 6 QUICK WINS, 10 ARTICLE IDEAS, 30 KEYWORDS FOR THELIBRARIAN