Ahrefs MCP is still on the same insufficient-plan key, every endpoint returns Insufficient plan including the free subscription-info-limits-and-usage. So this run is again a manual SEO audit on the served HTML and source code, plus a deploy-state check.
The big finding: the May 3 SEO fixes are committed in slate-landing but never reached production. Local main is 2 commits ahead and 9 commits behind origin/main, so a plain git push would either be rejected or clobber 9 origin commits. The user needs to merge or rebase before pushing.
Applied a second batch of code-level fixes today (hreflang, og locale alternates, per-post sitemap lastmod, app-subdomain noindex). Slate-landing changes are committed locally on top of the May 3 stack. Slate-app changes are on disk but the commit is blocked by a leftover .git/index.lock, so the user needs to clear that and commit manually.
GET subscription-info-limits-and-usage -> Insufficient plan
GET site-explorer-domain-rating -> Insufficient plan
GET site-explorer-metrics -> Insufficient plan
GET site-explorer-backlinks-stats -> Insufficient plan
GET site-audit-projects -> Insufficient plan
GET management-projects -> Insufficient plan
Until the Ahrefs plan is upgraded, the scheduled task can only do manual audits. Recommend either upgrading the API plan, or switching the task prompt to drive the Ahrefs UI through Claude in Chrome and screenshot the dashboards.
The live slateup.ai homepage today still serves the old build:
Slate — AI-powered Interactive Classroom (em dash) while the source uses a hyphen<link rel="canonical">, only the inline-JS canonical<noscript>You need to enable JavaScript to run this app.</noscript> (the H1 + internal link list from May 3 is missing)<meta name="author">assets.emergent.sh script on blog-route HTML filesGit log shows the local repo at:
080c708 seo: hreflang, og locale alternates, per-post sitemap lastmod, fix homepage title (today)
14fcb07 SEO: Add schema.org JSON-LD, noscript fallback, and May 4 blog posts (May 4)
63f319a feat: add new blog posts, update SEO scripts, and content updates (May 3) (May 3)
git status reports Your branch and 'origin/main' have diverged, and have 2 and 9 different commits each, respectively. Origin is ahead with PRs #1 Merge fix/audit-run-12-landing-bugs plus several blog post commits, none of which are in local. Local has the SEO fixes that are not on origin. Plain git push won't work without a merge.
Resolution path the user needs to run, ideally in this order:
cd slate-landing
git fetch origin
git log --oneline origin/main..HEAD # 3 local-only commits
git log --oneline HEAD..origin/main # 9 origin-only commits
git pull --rebase origin main # or merge, picking the strategy that fits
# resolve conflicts in frontend/public/index.html and frontend/scripts/inject-page-meta.mjs if any
yarn build # confirms inject-page-meta + sitemap still pass
git push origin main
Vercel will redeploy on push. Without that step, none of the May 3 or May 4 SEO fixes are live.