Auto-Fix

    Connect your site

    Auto-Fix is new. Nothing is written automatically: you see a before and after preview of every change, you approve each one, and every write can be reverted in a single click. A connection cannot apply anything until it passes a read-only check.

    What Auto-Fix needs to write to your site

    • WordPress — self-hosted, or WordPress.com on the Business plan or higher.
    • The site is served over HTTPS and runs WordPress 5.6 or newer.
    • Settings → Permalinks is set to anything other than 'Plain'.
    • An Administrator or Editor account you can generate an Application Password from.
    • Meta description fixes need Yoast SEO or Rank Math installed.
    • HubSpot and Salesforce connect by sign-in — no password to copy.

    Webflow, Wix, and Shopify are not supported yet. Tell us which one you use and we will prioritize it — we build the next connection off request volume. Scan ($19/mo) works on any site today, and for anything the agent cannot apply we hand you the exact copy and markup to paste.

    Step 1 · Try it on our sample site

    This runs entirely in your browser against janedoeco-demo.stackfinder.dev. Nothing here touches a real site — it is here so you can see exactly what a preview, an applied change, and a revert look like before you connect anything of your own.

    Write a meta description

    The pricing page has no meta description, so Google writes its own snippet from body copy.

    Write a page title

    The demo page title is the WordPress default, which costs clicks in search results.

    Add image alt text

    Most homepage images have no alt text, so screen readers and image search skip them.

    Same screens, same buttons, same revert path as a real connection.

    How to connect WordPress

    1. 1. Sign in to your WordPress admin

      Go to yourdomain.com/wp-admin and sign in with the account you want Stack Finder to act as. Every change the agent makes is attributed to this account in your WordPress revision history, so use a real Editor or Administrator account you are comfortable auditing.

    2. 2. Open your profile page

      In the left sidebar choose Users → Profile (on some setups it is Users → All Users, then click your own name). Scroll to the bottom of that page until you reach the section titled 'Application Passwords'.

      • If you do not see the section, your site is on HTTP rather than HTTPS, or a plugin has disabled the feature. Fix that first — Stack Finder cannot connect without it.
      • On multisite, generate the password on the site you want fixed, not the network admin.
    3. 3. Create the Application Password

      In the 'New Application Password Name' field type Stack Finder Auto-Fix, then click 'Add New Application Password'. WordPress shows a 24-character password in blocks, like abcd EFGH 1234 ijkl MNOP 5678. Copy it now — WordPress will never show it again.

      • This is not your account password. Stack Finder never asks for your login password and would refuse it anyway.
      • You can paste it with or without the spaces; we normalize it for you.
    4. 4. Paste the details into Stack Finder

      Back in Stack Finder, enter your site address (the full https:// address of the site you want fixed), your WordPress username (the login name shown on your profile, not your display name), and the Application Password you just copied. Then click Verify and connect.

      • Stack Finder makes one read-only call to confirm the credential works and to check your role. Nothing is written to your site during verification.
      • The Application Password is stored in an encrypted vault. It is never shown in the app again, never sent to your browser, and never included in reports or exports.
    5. 5. Review and approve each fix

      Nothing is written automatically. On your report, auto-fixable findings gain an 'Apply fix' button that opens a side-by-side preview of the exact before and after value. Only when you approve does Stack Finder write the change — and every write is logged with a one-click Revert.

    You can cut off access at any moment from WordPress itself: Users → Profile → Application Passwords → Revoke next to 'Stack Finder Auto-Fix'. The next time the agent tries to write, it simply fails; nothing on your site is left in a partial state.

    Add a WordPress site

    Your login name, not your display name.

    Never your account password. Spaces are fine.

    Verification is read-only. We check the credential works and what it is allowed to edit. Nothing is written to your site.

    If something goes wrong

    Still stuck? Send it straight to us instead of troubleshooting alone — report a connection problem.

    Other platforms

    We build the next connection off request volume. If you use something that is not supported yet, tell us and it goes to the top of the queue.

    WordPress (self-hosted)
    Available now

    Connect today with an Application Password. Titles, meta descriptions, image alt text and FAQ schema.

    HubSpot
    Coming next

    One-click OAuth connection, no password to copy. In build now.

    Salesforce
    Coming next

    One-click OAuth connection for record and page-layout fixes. In build now.

    Webflow
    Not supported yet

    Not supported yet. Tell us you use it and we will build it next — we sequence by request volume, not by guess.

    Wix
    Not supported yet

    Not supported yet. Tell us you use it and we will build it next — we sequence by request volume, not by guess.

    Shopify
    Not supported yet

    Not supported yet. Tell us you use it and we will build it next — we sequence by request volume, not by guess.