Connecting your website platform

What Auto-Fix can change on each platform, and where to get credentials.

Each platform exposes different capabilities, so Auto-Fix coverage varies:

  • Any website (JavaScript snippet) — page titles, meta descriptions, and image alt text on any site, no credentials needed. You paste a one-line script tag into your pages; approved fixes are served through it in visitors' browsers and picked up by Google when it renders JavaScript. Fixes appear within about 5 minutes of approval — no redeploy.
  • GitHub — for plain HTML sites deployed from a repository (GitHub Pages, Netlify, Vercel…). Beacon scans up to 50 .html files on your branch and commits approved fixes (titles, meta descriptions, image alt text) directly to the files. Connects with a fine-grained personal access token with Contents read & write on that repository.
  • WordPress — page/post titles, excerpts (meta descriptions), and image alt text. Connects with an application password.
  • GoDaddy — GoDaddy Managed WordPress sites only, with the same coverage as WordPress (titles, excerpts, image alt text) via an application password created in WP Admin. GoDaddy's Websites + Marketing builder has no public API and can't be connected.
  • Shopify — product SEO titles, meta descriptions, missing product descriptions, and product image alt text. Connects with a custom-app Admin API token.
  • Webflow — static page SEO titles and meta descriptions. Connects with a site token; applied changes go live on your next site publish.
  • Wix — missing Wix Stores product descriptions. Connects with an API key and Site ID.
  • Squarespace — missing store product descriptions. Requires a developer API key and the Commerce Advanced plan.

Which should I pick?

If your platform is listed, use its dedicated connection — fixes are written into your actual site content. If it isn't (custom sites, site builders without APIs, anything else), use the JavaScript snippet: it works everywhere, needs no credentials, and undoing a fix simply stops serving it. For hand-written HTML sites in a GitHub repository, the GitHub connection gives you real commits you can review in your git history.

The in-app Connection Guide (Learn → Connecting your site) walks through getting credentials for each platform step by step, including screenshots-level detail and troubleshooting for WordPress.

Your credentials are encrypted before storage and only ever used to read and write the specific content types listed above. The JavaScript snippet connection stores no credentials at all — only a public site token that identifies which approved fixes to serve.