WHAT'S REAL TODAY The free audit is live right now — no connection, no sign-up. WordPress is live too: connect with one application password and HitMind reads your site, writes drafts, and waits for you to press Publish. Shopify and Webflow are what we're building next, described exactly as we're building them — clicking Connect on those two tabs touches nothing real. See plans — self-serve billing is open, and your first 3 articles are free.
HitMind + WordPress
WordPress builds and runs the site. HitMind is built to make it get found — and keep making it better.
There's nothing to migrate. HitMind reads the site you already have, files drafts through the REST API WordPress already ships with, and measures the result in the Search Console property you already own — no plugin of ours, no new editor, no second admin to log into twice a day. Connect it with one application password; every draft lands in your Drafts box, and the Publish button stays yours.
LIVE TODAY — CONNECT WITH AN APPLICATION PASSWORDHitMind + Shopify
Shopify runs the store. HitMind is built to make it get found — and keep making it better.
Your theme, checkout and catalogue will never change hands. HitMind is designed to install like any other Shopify app, work through the Admin API on a scope list you'll be able to read before you press Install, and report the outcome in your own Search Console — not in a dashboard only we can see. None of that is connected yet; this is how we're building it.
ON THE ROADMAP — NOT CONNECTED YETHitMind + Webflow
Webflow designs and hosts the site. HitMind is built to make it get found — and keep making it better.
HitMind is designed to never open the Designer. It'll work through the Data API: read your site, pages and collections, write new items into the collections you already built and leave them staged, then come back 28 days after each one goes live with what your Search Console recorded. None of that is connected yet; this is how we're building it.
ON THE ROADMAP — NOT CONNECTED YETThree reasons this combination holds
The write path already exists. Every WordPress since 4.7 serves /wp-json, and an application password switches it on for one user in about thirty seconds — no plugin from us, no FTP, no theme edit. The integration is boring on purpose.
WordPress has no opinion about what you publish. It hands you an editor and a blank page; deciding which page is worth writing — and proving afterwards that it was — is not its job and never has been. That is the whole of HitMind's job: topics mined from your own Search Console queries, a full draft, a quality gate, then the receipt 28 days later.
The draft box is a real safety line, not a setting. HitMind only ever files drafts — you press Publish in your own wp-admin. And what lands there is an ordinary WordPress post from the first second: your theme, your permalink, your revisions. If you cancel tomorrow, nothing has to be untangled.
Shopify keeps the two fields that write your search snippet — global.title_tag and global.description_tag — behind an "Edit website SEO" accordion at the bottom of every product, collection and page. Nobody fills 400 of those by hand. The Admin API can write them, so HitMind does: one queued job you approve as a list.
Shopify gives you a blog and then leaves the room. No query data in the admin, no brief, no calendar — which is why the blog stops in March. HitMind takes topics from terms your store already collects impressions for, including the product and "X vs Y" queries already collecting impressions for, and writes the article or the collection copy that goes after them.
Some things Shopify won't let anyone change: the /products/, /collections/ and /blogs/ prefixes, the generated sitemap, the way collection pagination works. HitMind doesn't pretend otherwise. It works inside the rules — a 301 through the URL Redirects API when an approved change moves a handle — and a fix that is genuinely impossible on Shopify stays in your list marked "not fixable on Shopify" instead of quietly disappearing.
A Webflow blog is a CMS Collection, and Collections are exactly what the Data API is for. HitMind creates the item and fills every field your template binds to — body, excerpt, cover, SEO title, meta description — then leaves it staged. Your components, interactions and class system never enter the picture: this is data arriving in a template you already designed.
Webflow sites usually look finished and read thin: a beautiful home page, a five-post blog that stopped in March, and no query data anywhere in the product. Ranking is a volume-and-freshness job, and a design tool has no reason to help you win it. That's the half HitMind takes.
The boundary is exactly the API's boundary, and the product says it in the same words: anything in a Collection field or a page's SEO settings, HitMind can write. A new section in a template, a static page's layout, custom code in the head — it can't, and those come back as briefs. Nothing gets described as done when it's actually blocked.
The split, row by row
Two columns, equal weight. No score at the bottom — adding up a scoreboard here would mean one of us has to lose, and that is not what this page is about.
| Capability | WordPress handles | HitMind handles |
|---|---|---|
| Site structure & design | WORDPRESS Themes, the block editor, menus, permalinks, categories and tags. | HITMIND Doesn't touch any of it. When the fix lives in the template — a duplicated H1, a missing canonical — that finding stays in your fix list with the recommended change; HitMind doesn't edit templates. |
| What to write next | WORDPRESS Nothing. A blank editor and an empty calendar. | HITMIND Topics mined from your own GSC queries — the terms already collecting the most impressions — each one carrying its evidence: the query, the impressions, today's position. |
| Drafting & quality gate | WORDPRESS The editor and the revision history. The words are yours to write. | HITMIND Writes the full piece using only the brand facts you've approved, then scores it 0–100 on structure, length, keyword use, readability and links. Under 70, it's rewritten automatically, up to twice. It doesn't check originality or fact-accuracy — read each draft before you publish it. |
| Title tag & meta description | WORDPRESS Stores them — usually through Yoast or Rank Math fields. | HITMIND Drafts a title and a summary, and writes the summary into WordPress's own excerpt field — the one every WordPress site has, no plugin required. It doesn't write into Yoast, Rank Math or any other SEO plugin's fields; if your plugin reads its meta description from somewhere else, you'll want to copy it over by hand. |
| Structured data | WORDPRESS Plugins emit the site-wide basics: Organization, breadcrumbs. | HITMIND An Article JSON-LD block per piece, generated with the draft and written straight into the post body as a script tag. |
| Internal links | WORDPRESS You insert links by hand; related-post plugins match on tags. | HITMIND 2–5 links to articles HitMind has already published on your site — picked from the ones already confirmed live on WordPress, not just filed as drafts. It doesn't yet crawl the rest of your existing site for link targets. |
| Publishing & media | WORDPRESS The Publish button, the media library, scheduling. | HITMIND Files the finished piece as a draft as soon as it's approved — by you, or automatically if you've turned on auto drafts — with a nightly batch as backstop for anything that misses. It never presses Publish — you do, in your own wp-admin. It doesn't set a cover image; that's still yours to add in WordPress. |
| What happened after | WORDPRESS Nothing. WordPress doesn't know what Google did. | HITMIND 28 days after a piece goes live, prints a receipt: the 28 days before against the 28 days after, from your Search Console — clicks, impressions, position, which queries moved. Receipts that went down get printed too. |
On the WordPress tab, the HITMIND column is how it works today. On the Shopify and Webflow tabs, it describes what we're building, row by row — none of that is connected yet. The platform's own column is how things work today, with or without HitMind.
| Capability | Shopify handles | HitMind handles |
|---|---|---|
| Storefront & checkout | SHOPIFY Theme, templates, cart, checkout, inventory, payments, apps. | HITMIND Out of reach on purpose — HitMind never asks for write_themes. Theme findings (a second Product schema block, images with no width and height) come back as a brief naming the file. |
| URLs & sitemap | SHOPIFY Fixed /products/, /collections/ and /blogs/ prefixes; sitemap.xml generated for you; robots.txt.liquid in the theme. | HITMIND Reads all three in the audit. Creates a 301 through the URL Redirects API whenever an approved change moves a handle. Says "not fixable on Shopify" where that is the truth. |
| Title tag & meta description | SHOPIFY Two metafields per page, buried under "Edit website SEO". | HITMIND Drafts them for products, collections, pages and articles, then writes global.title_tag and global.description_tag in bulk — reviewed as one list, not 400 cards. |
| What to write next | SHOPIFY Nothing. A blog, and a text box. | HITMIND Topics from your own Search Console: product terms, use-case terms, comparison terms — each with its impressions and current position attached. |
| Blog articles | SHOPIFY Blogs, articles, authors, tags, comments. | HITMIND Writes the piece, runs the gate, creates it as an unpublished article on the blog you choose. You press Publish in the admin. |
| Product & collection copy | SHOPIFY body_html is yours to write, one editor at a time. | HITMIND Proposes rewrites in reviewable batches; on approval writes body_html plus the two SEO fields, keeps a snapshot of the old copy and reverts in one click. Needs write_products — decline it and everything else still runs. |
| Structured data | SHOPIFY Most themes emit some Product and Organization JSON-LD — and it varies by theme. | HITMIND Checks what your theme already emits first, then adds only what's missing — Article, FAQ, BreadcrumbList. It will not stack a second Product block on top of yours. |
| What happened after | SHOPIFY Shopify Analytics: sessions, conversion, orders — everything inside the store. | HITMIND The Search Console side: 28 days before against 28 days after, per URL. Reported next to Shopify's numbers, never merged into them — we don't put a revenue figure on an article we can't attribute. |
On the WordPress tab, the HITMIND column is how it works today. On the Shopify and Webflow tabs, it describes what we're building, row by row — none of that is connected yet. The platform's own column is how things work today, with or without HitMind.
| Capability | Webflow handles | HitMind handles |
|---|---|---|
| Design, templates & hosting | WEBFLOW The Designer, components, interactions, the CMS schema itself, hosting and CDN. | HITMIND Doesn't open it. Template-level findings — an H1 bound to the wrong field, an image with no alt binding — come back as a brief naming the element. |
| CMS items | WEBFLOW Collection structure, field types, template bindings, and the item limit on your plan. | HITMIND Creates the item and fills every bound field, staged and invisible to visitors. You press Publish in Webflow. |
| Page SEO fields | WEBFLOW Per-page and per-item SEO title, meta description and OG image settings. | HITMIND Drafts and writes them through the Pages API and the CMS fields. On a static page it changes the metadata only — never the page's content. |
| What to write next | WEBFLOW Nothing. A Collection with three items in it. | HITMIND Topics from your Search Console queries, plus the gaps a 600-page crawl finds: pages nothing links to, subjects your competitors cover and you don't. |
| Internal links | WEBFLOW You add them by hand, in the Designer or inside a rich text field. | HITMIND Inserts 3 real in-site links into the rich text body and verifies each one returns 200 before the item is filed. |
| Structured data | WEBFLOW Page custom code — which the API cannot reach — plus whatever embed field you bound in the template. | HITMIND Writes Article and FAQ JSON-LD into that embed field when it exists. When it doesn't, it hands you the one-time snippet and marks the item "blocked" — not "done". |
| Redirects & sitemap | WEBFLOW Auto sitemap.xml, robots.txt and the 301 table — all in site settings. | HITMIND Reads them in the audit. When an approved change moves a slug, it gives you the exact redirect row to paste — it does not write your site settings. |
| What happened after | WEBFLOW Webflow Analyze: page views and traffic inside the site. | HITMIND The Search Console side: 28 days before against 28 days after, per URL. When the two disagree, we explain that they count different things rather than quoting whichever is higher. |
On the WordPress tab, the HITMIND column is how it works today. On the Shopify and Webflow tabs, it describes what we're building, row by row — none of that is connected yet. The platform's own column is how things work today, with or without HitMind.
Interactive preview, not a live connection. WordPress is real and live — you connect it the same way, with an application password, from your HitMind dashboard; this widget just walks through what each failure looks like first, so nothing here touches your actual WordPress site. Shopify and Webflow aren't built yet — there's no real integration on those two tabs to preview.
One application password, one read-only Google grant
In WordPress: Users → Profile → Application Passwords → Add New, name it HitMind. WordPress shows you 24 characters in six groups; paste them once. It is not your login password — a login password never works here, by design — and it inherits the role of the user you created it for, so an Editor account keeps it away from plugins, users and settings. Search Console is a separate, read-only Google grant (webmasters.readonly), and it is the only place a number on a receipt is ever allowed to come from.
Paste the 24 characters WordPress gave you. Nothing happens on your site until you do.
Reads — from WordPress, only the status, link and publish date of the posts it has filed, so it knows when you've published them. Each time you connect or test the connection, it also creates one private test draft and deletes it again. Search Console is a separate Google grant: 16 months of queries, clicks, impressions and positions.
Writes — new posts in draft status, with their title, excerpt, JSON-LD and internal links. It does not edit your existing pages.
Revoke — one click in that same WordPress screen. It stops working immediately, no email to us, nothing to uninstall. Revoke the Google grant at myaccount.google.com/permissions. Drafts already filed are yours; receipts stop that day, and the app says so instead of estimating.
Everything on this page is what the platform's own API allows, not a private arrangement — read it at the source: WordPress REST API documentation ↗
OAuth, with the scope list on screen before you install
HitMind connects the way every Shopify app connects: you open the install link, Shopify — not us — lists the exact scopes being requested, and you press Install. No API key to paste, no custom app to create, no collaborator account. The list is short and deliberately asymmetric: broad read, narrow write, and no theme access at all. Search Console is a separate, read-only Google grant, and it stays the only source a receipt number may come from.
You approve the scopes on Shopify's own screen. Nothing happens in your store until you do.
Reads — read_content, read_products, read_themes: your articles, pages, products, collections, and what your theme already outputs, so nothing gets written twice. Plus Search Console, read-only.
Writes — write_content for articles and pages (created unpublished), write_url_redirects for the 301s you approved, and write_products only if you switch product rewrites on. write_themes is never requested, so the token cannot edit a .liquid file even if something goes wrong on our side.
Revoke — Settings → Apps and sales channels → HitMind → Delete. Shopify invalidates the token on the spot and we keep nothing that could reconnect. Articles already published stay in your store, under your domain, exactly as they are.
Everything on this page is what the platform's own API allows, not a private arrangement — read it at the source: Shopify access scopes documentation ↗
A site API token you generate, with the scopes you tick
In Webflow: Site settings → Apps & integrations → API access → Generate API token. You tick the scopes on that screen, Webflow shows the token once, you paste it into HitMind. There is no app of ours installed in your site and no OAuth prompt to think about. We ask for CMS and Pages; we do not ask for the scope that publishes your site — so the last click stays yours by construction, not by promise. Search Console is separate and read-only, and it remains the only source a receipt number may come from.
Create a site token in Webflow and paste it. Nothing happens on your site until you do.
Reads — sites, pages, collections and existing items, so it knows what you already published and which fields your template actually binds. Plus Search Console, read-only.
Writes — new CMS items (created as drafts), their bound fields, and page SEO metadata. It does not publish items, does not publish the site, and never deletes an item you already have.
Revoke — delete the token on that same settings screen; it dies immediately. Items already created stay in your CMS as drafts, to keep or bin as you like. Published pages are yours and stay published — we have no way to take one back, by design.
Everything on this page is what the platform's own API allows, not a private arrangement — read it at the source: Webflow Data API documentation ↗
Three you'd be right to ask
Do I have to install a plugin?
Can it break my site?
Only my blog is WordPress. The rest of the site isn't.
A receipt compares the 28 days before publish with the 28 days after, from your own Search Console. It is a measurement, not a claim about cause — a core update, a season, a competitor's move all land inside the same window. We print it that way, including the ones that went down.
Will it touch my theme or my checkout?
Can it rewrite 400 product descriptions?
My store is Shopify but the blog lives somewhere else.
A receipt compares the 28 days before publish with the 28 days after, from your Search Console: clicks and positions — never orders. Store revenue has a dozen causes in any given month, and an article that claims one of them is selling you a number, not a result.
Does it change my Designer file?
Will anything go live without me?
My plan has a CMS item limit.
A receipt compares the 28 days before publish with the 28 days after, from your Search Console. It's a measurement, not a cause: Webflow's own view counts, a core update and a seasonal dip all live inside the same window. The receipt prints either way — including the ones that went down.
Keep your stack. Add the part it doesn't do.
The audit needs nothing connected — it reads your homepage in about 60 seconds and says so on the report. WordPress connects today with one application password; Shopify and Webflow will connect once they ship, with one OAuth grant and one API token respectively. Or watch the 3-minute demo first.