Skip to content

SEO Content Hub on Your Own Domain: The SEO Content Platform With No Developer Needed

SEO Content Hub on Your Own Domain: The SEO Content Platform With No Developer Needed
Table of contents

If you're shopping for an SEO content platform, here's the short version: you want your articles living at yoursite.com/resources/article ✅, not blog.yoursite.com/article ❌. The good news is you can have an SEO content hub on your own domain, filled continuously, without hiring a developer, migrating your CMS or paying per seat. Here's how the routing works, exactly what you do on WordPress, Framer, Next.js, Netlify and custom stacks, and what you get once it's live.

Yes, there's a tool for that. As of October 2026, Hatter builds a Hub at yoursite.com/resources or yoursite.com/hub, finds Google and AI search opportunities, drafts articles in your brand voice and publishes them after you approve. A guided wizard (or our WordPress plugin) handles the routing, so there's no developer, no CMS migration and no per-seat fees.

Subfolder vs subdomain: why yoursite.com/resources wins the argument

A subdomain (blog.yoursite.com) is technically its own host. A subfolder, also called a subdirectory (yoursite.com/resources), is a path on the domain you already have. For readers the difference is cosmetic. For search engines and answer engines it's where the trouble starts.

To be fair to Google: its crawling and indexing FAQ says you should pick whatever is easiest to organize and manage, and that "from an indexing and ranking perspective, Google doesn't have a preference." Practitioners still lean hard toward subfolders, and here's why. Your homepage, product pages and backlinks all live on one host, and every article in a subfolder sits inside that same site's internal link graph, sitemap and crawl. Keeping content on one host consolidates backlinks, internal links and indexation signals, while a subdomain tends to be managed and linked like a separate property.

What's the difference for ChatGPT and Perplexity? AI assistants cite pages they can crawl as plain HTML on a domain they already trust, and a subfolder keeps your hub on the domain buyers (and models) already associate with your brand, alongside its links and reputation. And with 60% of Google searches now ending without a click, being the source an answer engine quotes matters more each quarter.

What subfolder, subdirectory and reverse-proxy publishing mean

Subfolder publishing (or subdirectory hosting) means content served by one system appears under a path on your main domain, like /resources. Reverse-proxy publishing is the plumbing that makes it work: when a visitor or crawler requests yoursite.com/resources/anything, a rewrite rule on your domain quietly fetches that page from the content platform and returns it under your address. The URL never changes, so search engines and AI crawlers see one site. You don't need a developer: on WordPress it's a plugin, on Framer it's a form in Site Settings, and on Next.js or Netlify it's a few lines pasted into a config file you already have.

Your options compared: native CMS, subfolder host, content generator or Hatter Hub

Whatever you pick, look for a tool that serves pages on your root domain, server-renders them and handles writing as well as hosting. Most tools solve half the job. Subfolder blog hosts give you the path and an editor, but you still write everything. AI content generators write, but push drafts into a CMS you have to run and format. A native CMS gives you pages, and nothing else. Here's how the routes stack up as of October 2026.

OptionOn your domainNeeds a developerCMS migrationWho finds topicsWho writesAI citation trackingLead captureLead attribution (Google vs AI)Pricing model
Native CMS (Webflow, Framer)YesVaries by siteNoYouYouNoBuild it yourselfNoYour site builder plan
Subfolder blog hostYes, via proxyOne-time routingNoYouYouVaries by vendorVaries by vendorVaries by vendorVaries by vendor
AI content generator into your CMSYes, inside your CMSVaries by vendorNo, but it writes to your CMSPartly automatedAI, you edit and formatVaries by vendorWhatever your CMS hasVaries by vendorVaries by vendor
Hatter HubYes, at /resources or /hubNo: guided wizard, WordPress plugin or a pasted rewrite ruleNo, never writes to your CMSSEO and AEO agentsAgents in your voice, you approveYes: ChatGPT, Perplexity, Gemini, AI OverviewsLead form or CTA banner on every pageYes, page by page$1,500/mo self-serve or $3,500/mo Managed (6-month minimum), no per-seat fees

Honest note: if all you want is hosting for posts you'll write yourself, a subfolder blog host is cheaper than we are. Hatter earns its fee when you also want the research, the writing, the approvals, the AI visibility tracking and the leads handled.

How the Hatter Hub gets onto your domain, step by step

The Hub is a resources section that we host and publish, served under a path on your domain. As our product reference puts it, your side is routing the path to Hatter, adding the Hub sitemap to robots.txt and linking it from navigation. The connection wizard in the app walks you through all of it for your specific host. Here's the full sequence.

  1. Pick your path (the slug). Usually /resources, /hub or /blog. You choose it during onboarding and can update it later. Pick one you'll keep for years, because URLs that stay put keep their authority.
  2. Tell the wizard where your site is hosted. WordPress, Next.js, Netlify, Framer or a custom implementation. The wizard then shows the exact steps for that platform. You also get a tenant ID, which maps to [tenantId].hatter.dev, the origin that serves your Hub.
  3. Point the slug at your tenant. On WordPress you install our plugin. On Framer you add a Multi Site rewrite rule. On Next.js or Netlify you paste a rewrite rule we give you. Everything else on your site keeps loading exactly as it does today.
  4. We verify, and the Hub goes live. The wizard probes your site under the slug to check it can reach the Hub. That check is not just a check: the first time it succeeds, the Hub is marked connected and starts serving in the same moment. There is no separate "publish the hub" button to hunt for.
  5. Publish your first article. A freshly connected Hub serves an empty index, so the connected screen sends you straight into the launch flow, where you pick from your drafts and publish. Connecting and publishing are both free.
  6. Submit the sitemap and link the Hub. The wizard then guides you through submitting the Hub sitemap (served under your slug, so for /hub that's yoursite.com/hub/sitemap.xml) to Google Search Console. We also recommend adding it to robots.txt and putting a "Resources" link in your header or footer, so visitors and crawlers know the section matters.

Does it ever write into your CMS or change existing pages? No. Hatter only serves the Hub under its slug. Your CMS is never written to, and your existing pages are never edited or rewritten. Even the WordPress plugin only listens for requests under the Hub slug; it doesn't touch your posts, pages or theme.

Here's what happens when someone (or something) visits a Hub page:

Visitor or crawler → yoursite.com/resources/guide → rewrite rule on your domain → [tenantId].hatter.dev serves the page → URL stays yoursite.com/resources/guide

And a sample URL tree once the Hub has some meat on its bones:

  • yoursite.com/ (your existing site, untouched)
    • /pricing, /product, /about (still served by your CMS)
    • /resources (Hub home)
      • /resources/what-is-usage-based-billing (pillar page)
      • /resources/usage-based-billing-vs-seat-pricing (cluster article)
      • /resources/best-billing-tools-for-saas (cluster article)
      • /resources/sitemap.xml (Hub sitemap)

Platform notes: WordPress, Framer, Next.js, Netlify, custom stacks and Webflow

We support WordPress, Next.js, Netlify, Framer and any custom implementation. The customer-side steps are the same everywhere: point the slug at your tenant, let us verify, submit the sitemap, link the Hub.

WordPress

WordPress is the easiest route, because our plugin does the routing for you. Download the Hatter plugin as a zip from the wizard (it's also headed for the wordpress.org directory), install and activate it, then click the link in the wizard that opens the plugin's settings with your tenant ID pre-filled (or type it in by hand). The plugin picks up your slug from Hatter, listens for requests under that slug on your WordPress site and streams them from our servers. Your themes, plugins and existing posts stay untouched. Time on your side: install a plugin, paste one ID, done.

Framer

How do you add an SEO resource hub to a Framer site without a developer? For a simple blog you write yourself, use Framer's native CMS: it's built for exactly that. If you also want topics found, articles written in your voice, approvals, AI citation tracking and lead capture, a Hatter Hub on /hub runs alongside your Framer site with no CMS migration. The routing uses Framer's built-in Multi Site rewrite rules, so there's no Cloudflare Worker or external proxy to set up. In Framer, go to Site Settings → Hosting → Multi Site → Add a rule. Set the source path to your slug plus a wildcard (/hub/*), the rewrite type to External, and the destination to your tenant URL (https://[tenantId].hatter.dev/*). Publish the site, and we verify the connection. Two handy details from the same Framer doc: a rewrite takes priority over a Framer page on the same path, and Framer's built-in analytics only track the main project, which is one more reason the Hub's own lead tracking matters.

Next.js (including Vercel)

Path routing is native here. Add a rewrite to next.config.js or next.config.ts:

{ source: "/hub/:path*", destination: "https://[tenantId].hatter.dev/:path*" }

Deploy, and we verify the connection the same way. If you're hosted on Vercel, this is all the config you need; the rewrite ships with your project.

Netlify

Netlify handles this with a proxy rewrite, in either _redirects or netlify.toml. The status must be 200, so Netlify proxies the request instead of redirecting the visitor off your domain. The _redirects line is:

/hub/* https://[tenantId].hatter.dev/:splat 200

Or the equivalent netlify.toml block:

[[redirects]]
  from = "/hub/*"
  to = "https://[tenantId].hatter.dev/:splat"
  status = 200

Deploy, and we verify.

Custom implementation

On any other stack (nginx, Cloudflare, a Rails app, whatever you've built), we don't care what's serving your site. The wizard hands you your slug and tenant ID, you make /hub route to gethatter.hatter.dev wherever your path routing already lives, and we verify it the same way.

Webflow and Shopify

Webflow and Shopify are coming soon. The plan for Webflow is a reverse proxy following Webflow's own subdirectory reverse proxy example: we'll build it out as soon as a Webflow customer needs it. If you're on Webflow and want a Hub now, tell us during the free audit and we'll talk through the timeline.

What happens after setup: the always-on loop

Once the path is live, your only recurring job is approving drafts. In one sentence: Hatter researches keywords and AI prompts, plans pillar and cluster pages, writes them in your voice, links them internally, publishes under yoursite.com/resources after your approval, and keeps the hub updated.

  • Opportunities found. Our SEO Agent researches keywords on live search data and finds competitor gaps. Our AEO Agent mines the prompts buyers ask AI assistants and spots where competitors get recommended instead of you. The citation playbook covers how that works in detail.
  • Clusters, not a pile of posts. A content hub works when pillar pages link down to cluster articles and back up again, because a cluster of well-linked topic pages signals authority to Google and answer engines alike. Our site structure guide walks through the cluster content strategy.
  • Approval, then publish. Agents run continuously, but every draft waits for your sign-off in the launch flow.
  • Refreshes. Agents keep watching the prompts and keywords you've already won, and we recommend refreshing your best content every 90 days, as laid out in the always-on organic marketing engine.
  • Leads, attributed. Every Hub page carries a lead form or call-to-action banner, and our AI visibility dashboard shows Google-sourced and AI-sourced traffic side by side, page by page, plus who converts.

Making the hub readable by AI crawlers

What does it take for AI assistants to read and cite pages in a subfolder hub? Four things: a sitemap listed in robots.txt and submitted to Search Console so crawlers find new pages, server-rendered HTML so crawlers that don't run JavaScript still see the content, schema markup so machines can parse it, and bot settings that don't block the AI crawlers you want. As of October 2026, Hatter Hub pages are server-rendered and schema-marked by default, and the wizard walks you through the sitemap right after connecting. Bot settings live in your CDN or firewall, so check those yourself.

Server rendering isn't a nice-to-have. A Vercel and MERJ analysis found that none of the major AI crawlers it measured, including OpenAI's GPTBot, OAI-SearchBot and ChatGPT-User, Anthropic's ClaudeBot and PerplexityBot, render JavaScript. If your content only appears after scripts run, those crawlers see an empty page. Every Hub page is server-rendered, served from a global CDN and schema-marked for AI parsing.

Now the sneaky one: bot protection. In its Content Independence Day announcement, Cloudflare moved to block AI crawlers by default unless they pay, and its AI bot policy docs set new defaults for new domains from September 15, 2026: Training and Agent bots blocked on pages with ads, Search bots allowed, and mixed-purpose crawlers caught by any setting that blocks AI training. If your domain runs through Cloudflare, open Security Settings and confirm you're not quietly shutting out the crawlers you're trying to earn citations from. Check each vendor's docs too, for example OpenAI's crawler overview, which notes that OAI-SearchBot (search) and GPTBot (training) are controlled separately in robots.txt, so you can allow one without the other. Our technical SEO for AI answer engines covers AI-crawler access, robots.txt and rendering audits if you'd rather hand this off.

Proof: what a Hub on your own domain does

BSCG, a certification brand with 20 years of near-zero search presence, is our favorite example. As we document in our citation explainer, in 90 days 19 Hub pages were consistently cited across ChatGPT, Gemini and more, traffic grew 851%, search impressions grew 3,652%, and BSCG hit 90% AI search visibility on its top queries. The latest BSCG case study reports site traffic up 30x, with Hatter-created and updated pages driving 81% of clicks and 84% of impressions. Same domain, same brand, a resources section that finally pulls its weight.

Pricing and fit

How much does a tool that builds and fills an own-domain SEO content hub cost? As of October 2026, Hatter self-serve is $1,500 a month, billed monthly with no long-term contract, and includes the SEO and AEO agents, content in your voice, publishing to your Hub, approvals, and lead and AI visibility tracking. Hatter Managed is $3,500 a month with a six-month minimum and adds a dedicated senior strategist, human review of every piece and technical SEO. Neither plan has per-seat fees, there's no extra charge for connecting the Hub or publishing pages, and you can start with a free audit, no card required.

Full details are on our pricing page, and the Hatter overview explains what each tier includes. Hatter is a strong fit if organic discovery drives your pipeline and nobody on the team has spare hours to research, write and publish on an ongoing basis. It's not the right fit if you don't have a live site yet, or if you only want somewhere to host posts you'll write yourself.

FAQ

What is the difference between yourcompany.com/resources and blog.yourcompany.com?

Google says it has no ranking preference between subfolders and subdomains, but a subfolder shares your main site's links, crawl and internal linking, while a subdomain tends to be managed and linked like a separate property. For ChatGPT and Perplexity, a subfolder keeps your hub on the domain they already associate with your brand. That's why many practitioners prefer the subfolder.

Do I need a developer to set up subfolder publishing?

No. With Hatter, a guided wizard gives you a slug and a tenant ID and shows the exact step for your host: install a plugin on WordPress, add a Multi Site rewrite rule in Framer's Site Settings, or paste a rewrite rule into your Next.js or Netlify config. The wizard verifies the connection, and the Hub goes live the moment it succeeds. After that, every approved page publishes with no developer involved.

Which platforms does an own-domain content hub work with?

As of October 2026, the Hatter connection wizard supports WordPress (via our plugin), Next.js, Netlify, Framer and any custom implementation where you can route a path to your tenant URL. Webflow and Shopify are listed as coming soon and aren't selectable yet.

Should I use my site builder's native CMS, a subfolder blog tool, or a tool that also researches and writes?

Use the native CMS or a subfolder blog tool if you have the time and people to research and write every article yourself. Choose a platform like Hatter if you want topics found, drafts written in your voice, AI citation tracking and lead attribution handled for you, all on your own domain.

Will the content hub match my website's design, and can every page capture leads?

Yes on design, and every page carries a conversion point. An agent reads your site and styles the Hub to your colors, fonts and layout. Every Hub page carries a lead form or a call-to-action banner, and the dashboard shows which pages bring in the people who convert.

Who owns the content and the URLs on the hub?

The URLs live on your domain, not a subdomain or a rented platform, so the traffic, rankings and citations they earn accrue to your site rather than ours. For the contractual terms on content ownership, exporting articles and what happens to the hub if you ever leave, ask us before you sign; it's a fair question to put to any vendor.

Start with a free audit

Want to see what your hub would go after first? Start a free SEO and AEO audit and you'll get the first opportunities from our agents, no credit card required. If you've been hunting for an SEO content platform that puts the hub on your own domain and keeps it full, this is the quickest way to see it on your own site.

Ready to get leads?

First call is free. No commitment. No fluff.