Skip to content

fix(seo): clear residual audit errors — squareup redirect + contact email (MARTECH-19 follow-up)#1012

Open
juan-arcadedev wants to merge 1 commit into
mainfrom
juan/martech-19-residual-audit-errors
Open

fix(seo): clear residual audit errors — squareup redirect + contact email (MARTECH-19 follow-up)#1012
juan-arcadedev wants to merge 1 commit into
mainfrom
juan/martech-19-residual-audit-errors

Conversation

@juan-arcadedev

Copy link
Copy Markdown
Contributor

What

Follow-up cleanup after the MARTECH-19 re-crawl (docs.arcade.dev health 81 → 95, errors 143 → 39 URLs). Clears two of the residual error rows that are fixable in-repo.

Related: MARTECH-19 (merged), MARTECH-17 (page-size, separate).

Changes

1. Stale squareup auth-provider link → redirect
The crawl's "Broken redirect" + one of the 404/4XX rows is /references/auth-providers/squareup → 307 → /en/...squareup (404; the real page is square). There's no internal link to it in the repo, so it's an external/stale backlink. Added a redirect /:locale/references/auth-providers/squareup → /:locale/references/auth-providers/square, which turns it into 308 → 200 and clears the broken-redirect + that 404/4XX.

2. contact-us "Email Support" card → client-deferred mailto
contact-cards.tsx was the last raw mailto: (the flagged MARTECH-19 follow-up). It now assembles the mailto: after mount (same approach as <ContactEmail>), so the SSR/crawled markup is a plain /en/resources/contact-us link and Cloudflare has nothing to rewrite into a broken /cdn-cgi/l/email-protection link.

Deliberately NOT in this PR

  • "Canonical URL has no incoming internal links" (2: pagerduty-api, notion) — these are transient data-churn artifacts, not a code bug: notiontoolkit.json is now isHidden, and pagerdutyapi.json's category moved to customer-support, so the crawled …/development/pagerduty-api and …/productivity/notion pages won't be generated by the current data. They self-heal on the next build/deploy + crawl. No code change made (forcing one would be fixing a non-bug).
  • The rest of the email-protection cluster (~14 "links to broken page") — these come from auto-generated content Cloudflare reads as emails: connection strings in tool docs (e.g. mongodb+srv://user:p@ss@host) and example addresses in guide code blocks. The only clean fix is the Cloudflare Email Obfuscation toggle, which we've decided not to flip; an in-repo workaround would mean mangling generated tool data / example code, which isn't worth it.

Testing

  • pnpm build ✓ · pnpm test613 passing ✓ · pnpm lint — 0 errors ✓
  • Local prod server: contact-us SSR has 0 mailto:/email occurrences (renders the contact-page link); /en/references/auth-providers/squareup308…/square.

🤖 Generated with Claude Code

…t email

Follow-up cleanup after the MARTECH-19 re-crawl (health 95, errors 143->39):
- Redirect /:locale/references/auth-providers/squareup -> .../square. An
  external/stale link to the old "squareup" slug 404'd; this clears the
  "broken redirect" plus its 404/4XX rows.
- The contact-us "Email Support" card now assembles its mailto after mount
  (mirrors <ContactEmail>), so SSR markup is a plain contact-page link and
  Cloudflare can't rewrite it into a broken /cdn-cgi/l/email-protection link.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 13, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jun 13, 2026 12:36am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant