TL;DR

Ahrefs MCP still returns Insufficient plan on every endpoint (day 9). Manual audit on the live site and the local repo.

The local source for both repos has every SEO fix from the past week applied: em dashes removed, meta keywords gone, hreflang in place, static canonical, JSON-LD schema, og:locale alternates, app.slateup.ai noindex + robots.txt. The blog folder now has 142 posts, all em-dash-free, including 6 new uncommitted ones.

The live site is still serving the build from May 2. That is now a 4-day deploy gap. Nothing I edit on disk takes effect until the local repo can pull, rebase, and push to origin.

No new source edits today. Today is purely a status check.

Ahrefs API status

Still insufficient plan on every tool tried: management-projects, site-audit-projects, site-audit-issues, site-explorer-domain-rating, site-explorer-metrics, site-explorer-backlinks-stats. Unchanged since Apr 28. To resume programmatic audits, the Ahrefs MCP plan needs to be upgraded.

Live site: slateup.ai

Check Live (old build, May 2) Local source
title Slate — AI-powered Interactive Classroom (em dash) Slate, AI-powered Interactive Classroom
og:title Em dash version Comma version
twitter:title Em dash version Comma version
description with AI classmates — not just a chatbot with AI classmates, not just a chatbot
meta keywords Still present Removed
hreflang Missing en + x-default present
Static canonical Inline JS injects at runtime Static <link rel=canonical> • inject-page-meta.mjs
og:locale:alternate Missing en_US, en_GB present
JSON-LD schema Present (Org + WebSite) Present
robots meta index, follow index, follow
robots.txt Allow: / + sitemap (correct) Same
Sitemap 110 URLs, all lastmod 2026-05-02 generate-sitemap.mjs uses today's date

Live site: app.slateup.ai

Check Live Local source
robots meta on / None (homepage indexable) robots: { index: false, follow: false } in app/layout.tsx
robots.txt 404 User-agent: * / Disallow: / in public/robots.txt
sitemap.xml 404 (correct for auth-only app) n/a

Both changes are uncommitted in Slate-app. Branch is up to date with origin so a single commit + push will deploy.

What is on disk and ready to ship

slate-landing (3 commits ahead, 9 behind, lock blocking)

Slate-app (clean, just needs a commit)