Askie for Schools SEO Audit
Your site barely shows up on Google for the searches your audience is running. Here's what's broken, and the 40k+ monthly searches you could rank for instead.
Start here · top 5 fixes
- 01Build authority before publishing more content
- 02Consolidate the subdomain under the root domain
- 03Target the 'ai homework helper' cluster first when authority arrives
- 04Add the schools landing page to the main site's navigation and internal link network
- 05Fix em dashes in page titles and meta descriptions
What's wrong, why it matters, and how to fix it.
7 structural issues.
Read full assessment
kidsai.app has 160 published URLs, valid schema markup, proper HTTP status codes, and meta descriptions on every fetched page. The technical foundation (crawlable pages, structured data, sitemap) is in place. The site also covers a genuine product niche with real differentiation (child-safe AI with COPPA compliance, parental controls, age-adaptive responses). Five comparison pages and multiple feature pages show an understanding of bottom-funnel content shapes.
The problem is execution. Zero ranked keywords across 160 pages is a domain-level suppression signal. Every page is inflated to 8,000-15,000 words regardless of intent (a contact page does not need 14,787 words). The content reads as AI-generated at scale, with identical page templates, emoji-laden headings, and uniform structure. The /tools/ (35 URLs) and /topics/ (31 URLs) sections add 66 programmatic pages that match Google's "scaled content abuse" pattern. The schools.kidsai.app subdomain has no independent content, and the parent domain's content targets parents rather than the stated audience of teachers and administrators. Before any new content is published, the existing 160 pages need aggressive pruning and rewriting. The site's recovery depends on reducing URL count by 40-50% and proving quality on the remainder.
01Every page is stuffed to 8k-15k words, including utility pages that should be 200 words
PROGRAMMATIC BLOAT
The Contact page is 14,787 words. The FAQ is 14,686. The app download page is 14,277. A parent guide runs 15,097. Every single fetched page lands between 7,800 and 15,100 words, regardless of page type. This uniformity is a hallmark of AI-generated template padding. Google's March 2024 and August 2024 Helpful Content updates specifically target sites where content volume is artificially inflated without corresponding user value. A contact page needs a form and an email address, not 14,000 words of filler. With 160 indexed URLs and zero ranked keywords across all of them, the domain shows clear signs of site-wide quality suppression.
Show more
Google is treating the entire domain as low-value, and this word-count inflation is the most likely trigger.
4 evidence points
- ·Contact page: 14,787 words (typical contact page: 100-300 words)
- ·FAQ page: 14,686 words; Apps download page: 14,277 words
- ·Parent guide: 15,097 words; schools landing: 10,439 words
- ·160 URLs indexed, 0 ranked keywords across all pages
The fix
1. Audit every page and set a target word count appropriate to its intent (contact: 200, FAQ: 1,500, comparison: 2,000-3,000, landing pages: 1,500-2,500).
2. Strip all filler paragraphs that repeat the brand name or restate the same benefit in different words.
3. Prioritize the 10 highest-intent pages (schools landing, comparison pages, homework help) for manual rewrite.
4. After trimming, request re-indexing via Google Search Console for each cleaned page.
5. Monitor crawl stats in GSC for 30 days to see if Google increases crawl rate (a positive signal of quality reassessment).
02160 published URLs produce zero organic rankings, signaling domain-level quality suppression
INTENT ALIGNMENT
Zero page-1 keywords. Zero page-2 keywords. Zero page-3 keywords. The site has published 160 URLs across 6 content buckets (blog, tools, topics, ai-for-kids, comparison pages, landing pages) and Google surfaces none of them for any query. This is not a crawlability problem (pages return 200, schema is present, titles and metas exist). This pattern matches what Google calls a 'site-wide signal' in its quality rater guidelines: when enough low-quality content exists, the classifier suppresses the entire domain rather than individual pages.
Show more
The inflated word counts, the AI-generated content patterns, and the sheer volume of thin programmatic pages (/topics/ at 31 URLs, /tools/ at 35 URLs) all feed this classifier. Recovery requires pruning the weakest content and proving quality on the remaining pages before Google will reassess.
4 evidence points
- ·Total ranked keywords: 0 (page 1: 0, page 2: 0, page 3+: 0)
- ·Total estimated organic traffic value: $0
- ·160 URLs in sitemap across 6 content buckets
- ·All fetched pages return 200 with valid titles, metas, and schema markup
The fix
1. Connect Google Search Console and pull the full index coverage report to confirm how many of the 160 URLs are actually indexed vs. 'Discovered, not indexed' or 'Crawled, not indexed'.
2. Identify all URLs in 'Crawled, not indexed' status. These are pages Google chose not to index after seeing the content.
3. Noindex or 410 the bottom 50% of pages by quality (likely most /topics/ and /tools/ pages).
4. Consolidate the remaining content into fewer, genuinely useful pages.
5. Resubmit the pruned sitemap and monitor index coverage weekly.
03Schools product targets teachers and admins, but 90%+ of content targets parents
INTENT ALIGNMENT
The brief defines three audiences: K-12 teachers, school administrators, and parents. The content strategy calls for teacher how-to guides, admin safety explainers, and district procurement buyer's guides. But the actual site content is almost entirely parent-facing. Pages like 'Parent's Guide to Askie,' 'Parent Resources,' 'AI Safety for Kids: What Every Parent Needs to Know,' 'AI Bedtime Stories,' and 'Is ChatGPT Safe for Kids?' all speak to individual parents, not educators. The single /schools landing page is the only page addressing the institutional buyer.
Show more
Teacher lesson-plan integration, classroom deployment guides, and district procurement content are completely absent. The keyword pipeline confirms this gap: 27 pillar opportunities exist for terms like 'ai homework helper' and 'ai for classrooms,' but the site has zero content mapped to these educator-intent queries.
4 evidence points
- ·Parent-facing pages: parent-guide, parent-resources, ai-safety-for-kids, ai-bedtime-stories, is-chatgpt-safe-for-kids
- ·Only 1 URL in /schools/ bucket out of 160 total
- ·Keyword pipeline: 27 pillar opportunities for educator terms like 'ai homework helper' and 'ai for classrooms'
- ·Brief lists teachers and school administrators as primary audiences
The fix
1. Build a dedicated /schools/ content hub with at least 8-10 pages targeting educator and admin queries (lesson plan templates, classroom setup guides, district evaluation criteria).
2. Create content for the 27 pillar keyword opportunities the pipeline identified, starting with 'ai for classrooms' and 'ai homework helper' from the teacher angle.
3. Add teacher-specific landing pages that address procurement objections (FERPA compliance, SSO, rostering, pricing per seat).
4. Separate the parent content from the educator content in navigation and internal linking so Google can cluster topical authority for each audience.
0466 programmatic pages across /tools/ and /topics/ with no ranking signal
PROGRAMMATIC BLOAT
The /tools/ bucket holds 35 URLs and /topics/ holds 31 URLs, totaling 66 programmatic pages. These represent 41% of the entire sitemap. The /tools/ index page alone is 7,808 words and links to 63 internal pages. For a site with zero organic rankings, these programmatic sections are dead weight. Google's spam policies updated in March 2024 explicitly call out 'scaled content abuse,' defined as generating many pages for the primary purpose of manipulating search rankings. Even if that was not the intent, the output matches the pattern Google penalizes. Each of these pages competes for crawl budget with the higher-value landing pages and blog posts that could actually rank.
4 evidence points
- ·/tools/ bucket: 35 URLs; /topics/ bucket: 31 URLs (41% of 160 total)
- ·/tools index page: 7,808 words linking to 63 internal pages
- ·0 ranked keywords across entire domain including these sections
- ·Google March 2024 update targets 'scaled content abuse' pattern
The fix
1. Pull Search Console data for every /tools/ and /topics/ URL to check index status and impressions.
2. Any page with zero impressions over 90 days should be noindexed and removed from the sitemap.
3. Keep only tools and topics pages that have unique, genuinely useful interactive content (not just text).
4. Consolidate related /topics/ pages into their parent category pages to reduce URL count.
5. After pruning, update the sitemap.xml to reflect only the pages you want indexed.
05Comparison pages use branded 'Askie vs X' framing that cannot rank for unbranded queries
CONTENT GAP
The site has at least 5 comparison pages: Askie vs Khan Academy Kids, Askie vs ABCmouse, Askie vs Google Kids Space, Askie vs Amazon Kids+, Askie vs Epic! Kids Books. Every title leads with the brand ('Askie vs X'). Users searching for edtech comparisons search 'Khan Academy vs ABCmouse' or 'best AI learning apps for kids,' not 'Askie vs Khan Academy.' When a brand has zero search volume for its own name, leading comparisons with that brand name means the title tag does not match any real search query. The H1s repeat the same pattern. These pages also run 8,500-9,100 words each, far longer than the 2,000-3,000 words typical of comparison content that ranks.
4 evidence points
- ·5 comparison pages all titled 'Askie vs [Competitor]'
- ·0 branded search volume means 'Askie' in the title matches no queries
- ·Word counts: 8,568 to 9,114 per comparison page (2-3x typical)
- ·Competitor keyword pipeline returned 0 opportunities
The fix
1. Reframe titles to lead with the comparison users actually search: 'Khan Academy Kids vs Askie' or 'Best AI Learning Apps for Kids Compared (2026).'
2. Trim each comparison page to 2,000-3,000 words of genuinely differentiated content.
3. Add a hub page at /compare/ or /alternatives/ that links to all comparison pages, targeting the category query 'best AI apps for kids.'
4. Include comparison schema (Product schema with review) to qualify for rich results.
06schools.kidsai.app subdomain isolates the schools product from the parent domain's content
SITE ARCHITECTURE
The audit target is schools.kidsai.app, but all 160 URLs in the sitemap live on kidsai.app (the root domain). Google treats subdomains as separate entities for ranking purposes. If schools.kidsai.app is the intended entry point for educators, it inherits none of the link equity, content signals, or topical authority from kidsai.app's 160 pages. The single /schools page on the root domain is the only bridge between the two. This architecture forces the schools product to build authority from scratch on a subdomain while the parent domain's content (however bloated) at least has age and crawl history.
3 evidence points
- ·Audit target: schools.kidsai.app; all 160 sitemap URLs on kidsai.app
- ·Only 1 URL in /schools/ bucket on the parent domain
- ·Google treats subdomains as separate sites for ranking signals
The fix
1. Decide whether the schools product lives at schools.kidsai.app (subdomain) or kidsai.app/schools/ (subdirectory).
2. If subdirectory: 301 redirect schools.kidsai.app to kidsai.app/schools/ and build the educator content hub there.
3. If subdomain: the subdomain needs its own sitemap, its own GSC property, and its own content strategy independent of the parent domain.
4. Do not split the target audience across two domains without a clear technical reason (e.g., separate app infrastructure).
07AI-content signals are visible across titles and page structure
TRUST SIGNALS
Multiple titles contain em dashes, a common AI-generation tell: 'Askie vs Khan Academy Kids . Free Curriculum vs AI Conversation (2026),' 'Askie vs ABCmouse . AI Conversations vs Gamified Drills (2026).' The /tools page title literally contains an em dash. H2 headings use emoji prefixes (the science beaker, lock, envelope emoji in headings on the FAQ, contact, and educational activities pages). Every page follows an identical structural template: 6 H2s, FAQ section, CTA section. The uniformity across 87 fetched pages, combined with the inflated word counts, creates a pattern that both Google's classifiers and human reviewers associate with scaled AI content.
Show more
For a product selling AI safety to schools, having visibly AI-generated marketing content undermines the trust proposition.
4 evidence points
- ·Em dashes in titles: /tools, /askie-vs-khan-academy-kids, /askie-vs-abcmouse, /askie-vs-google-kids-space
- ·Emoji in H2 headings on /faq, /contact, /educational-activities, /ai-safety-for-kids
- ·Identical 6-H2 + FAQ + CTA template across all 87 fetched pages
- ·Word count uniformity: every page between 7,800 and 15,100 words
The fix
1. Remove em dashes from all title tags and replace with pipes, colons, or periods.
2. Remove emoji from H2 headings site-wide.
3. Vary page structure across content types. Not every page needs 6 H2s and an FAQ.
4. Manually rewrite the top 15 pages with genuine editorial voice, specific examples, and real teacher/parent testimonials.
5. Run the cleaned content through an AI detection tool and iterate until scores drop below detection thresholds.
How AI-written does this site read?
3 pages analysed for AI-writing patterns.
Scored 62/100 across 3 pages. The content reads AI-heavy: formulaic structure, multiple categories of tells (18 flagged), and no consistent editorial voice. A core update is likely to demote these pages.
01/blog/how-to-talk-to-kids-about-ai1,652 words · 21 em dashes · 6 tells62
- EM DASH
“a real answer — not a dismissal, not a lecture”
Mid-sentence em dash as clause separator. A human editor would use a colon or period here.
- EM DASH
“Children who understand what AI is — even at a basic level — make better decisions”
Paired em dashes for a parenthetical aside — the most common LLM em-dash pattern. Commas or parentheses would be the human edit.
- EM DASH
“No judgment — just curiosity”
Em dash as dramatic pause between two short fragments. Classic unedited LLM punctuation.
- EM DASH
“AI is a tool that amplifies human capability — for better and worse”
Em dash before a stock closing phrase. Eight em dashes across the piece is a strong unedited-AI signal.
- OTHER
“They're less likely to over-trust it, less likely to be frightened by it, and more likely to use it”
Rule-of-three parallel construction with identical clause scaffolding — LLM default rhythm for adding rhetorical weight.
- OTHER
“It recommends what they watch, powers the voice assistants they talk to, filters the content they see”
Four perfectly parallel subordinate clauses stacked in one sentence. This cadence is formulaic LLM list-building, not natural prose.
02/blog/how-to-use-ai-safely-in-schools1,603 words · 31 em dashes · 6 tells62
- EM DASH
“isn't about whether — that argument is over. It's about how.”
Em dash as clause separator in the opening paragraph; a human editor would use a period or semicolon.
- EM DASH
“Consumer chatbots — ChatGPT, Gemini, Claude in their public consumer form — are not designed”
Paired em dashes for a parenthetical. LLMs default to this over commas or parentheses.
- EM DASH
“There is no AI-safety silver bullet — there's just whether you've done the unglamorous work”
Another mid-sentence em dash where a period or colon would read more naturally.
- EM DASH
“Banning rarely works — students access it on personal devices.”
Em dash in the FAQ section; 8 total across 1600 words is heavy AI signal regardless of prose quality.
- NOT JUST X, BUT Y
“Teach AI literacy, not just AI use”
Classic 'not just X, but Y' heading construction. Standard LLM scaffolding for adding depth to a list item.
- OTHER
“Done well, AI accelerates learning, frees teachers from grading, and helps the students who need the most one-on-one attention. Done badly, it leaks student data”
Rule-of-two parallel opener (Done well / Done badly) is a signature LLM rhetorical device for framing articles.
03/blog/how-ai-helps-kids-learn-science1,437 words · 23 em dashes · 6 tells62
- EM DASH
“Kids ask the best science questions — and most parents run out of answers fast.”
Em dash as casual clause joiner in the opening hook. A human editor would use a period or comma.
- EM DASH
“like a recipe book — that tells your body how to grow”
Em dash mid-explanation where a comma or "that" alone would suffice.
- EM DASH
“real science while being honest about what we don't yet know — which is itself an important scientific lesson”
Em dash parenthetical that reads as unedited LLM output.
- EM DASH
“That's what good AI learning tools do — they keep the chain of curiosity unbroken.”
Em dash as sentence-closer in the final paragraph — the classic LLM sign-off rhythm.
- OTHER
“Space and Astronomy...Animals and Biology...Weather and Earth Science...The Human Body”
Four parallel subsections each follow the identical formula: kid questions in quotes → AI-can-explain → broader concept name-drop. Rule-of-four scaffolding.
- STOCK PHRASE
“These questions about their own bodies make science deeply personal and relevant.”
"Deeply personal and relevant" is generic filler phrasing that avoids saying anything specific.
What you currently rank for.
30 keywords to win. 9 articles to write.
Highest-leverage first. Keywords with a ready article on top.
Authority comes before content here. The opportunities below won't rank without link signals first.
Start with general business directories that fit your niche. browse our directory of 100+ free sources.
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.
kidsai.app/toolskidsai.app/askie-vs-khan-academy-kidskidsai.app/askie-vs-google-kids-space - Title tag too short3 pages
Under 30 characters. Likely missing keyword context.
kidsai.app/contactkidsai.app/parent-resourceskidsai.app/privacy - Meta description too short3 pages
Under 120 characters. Wasting SERP real estate.
kidsai.app/contactkidsai.app/parent-resourceskidsai.app/educational-activities
SITE PROFILE
- Name
- Askie for Schools
- Audiences
- K-12 teachers looking for safe classroom AI tools · School administrators evaluating edtech platforms · Parents researching age-appropriate AI for children
- Locale
- EN / US
- Sitemap pages
- 87
Want us to fix these for schools?
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 · 5 QUICK WINS, 9 ARTICLE IDEAS, 30 KEYWORDS FOR SCHOOLS