AutoPSEO hosting: optional serving of your articles

AutoPSEO can serve your articles itself, so they have an address before your own site is ready to render them. The setup we recommend is delivery: your site receives every article through the webhook, stores it, renders it in its own templates and keeps it if you ever leave. Hosting is the fallback and the opt-in extra. This page covers what it serves, how to switch it off, and how hosted pages can follow your site's own look.

Hosting is on until you send articles to your site

Turning the engine on gives the property a hosted address at <name>.autopseo.com, where the name comes from the first label of your domain (3 to 40 letters, digits and hyphens; a reserved word gets a suffix, and a number settles a clash). Article URLs point there until you change it. The Where articles are published section says so: "AutoPSEO hosts the articles until you send them to your own site."

Once your webhook is set up, both can run side by side, and the page warns: "Both are on, so each article lives at two addresses. Once your site shows the articles, stop hosting them on AutoPSEO."

• Stop hosting on AutoPSEO needs a webhook that answered its last test and Your site's address. Every live article moves to your site's address and is sent to your webhook again as article.published.
• Host on AutoPSEO again moves the article URLs back to the hosted address. Nothing is sent to your site.
• While hosting is off, the webhook cannot be removed, because it is the only place your articles are published.

Why delivery to your own site is recommended

• You own the content. Every article and cover sits in your own system, so your site keeps working the day you stop using AutoPSEO.
• One address per article. With both on, the same article exists twice. Google's guidance on consolidating duplicate URLs explains why one canonical address is better.
• Your site stays in charge. Your templates, navigation, analytics and consent banner apply to the articles like to any other page, and your site can refuse anything it does not want (delivery).

What the hosted pages serve

• A request that prefers text/markdown gets the article as Markdown.
• A trailing slash, an old address without the type's path, and a merged article answer with a 301. A taken-down article answers 410 Gone, and an unknown address 404 with noindex.
• Every response carries X-AutoPSEO: 1. The generic pages send a strict Content-Security-Policy and are cached for five minutes.
• AutoPSEO pings IndexNow for hosted addresses with its own key, which Bing and Yandex read; Google does not use IndexNow (IndexNow).

Pages in your site's own look

While hosting is on, each full scan learns templates from your own pages, so a hosted article can look like the rest of your site. It learns one template per content type, kind of page (article, category or index) and language, only for types AutoPSEO writes that have at least two live articles, and never from pages AutoPSEO serves itself. Each template is checked by rendering your sample pages back and scoring how much of the original text it reproduces, in order, with the page head (title, description, canonical, hreflang, Open Graph) compared too. Where a language has no learned template, the generic pages are served.

Your site's scripts and response headers come along only when the article's canonical address is on your own domain; on an autopseo.com address the strict policy applies.

The Your pages on AutoPSEO section of the Your site page shows the scores per kind of page ("Lowest match across languages") and previews. Check every page compares each address with what your site serves now: the status and redirect target, the head (title, description, canonical, robots, hreflang, Open Graph and structured data), the links in the body, and the visible words in order. Each page comes out Identical, Close to identical, Different or Failed. The check runs when you start it.

Taking a section over as your site serves it

For a section AutoPSEO does not write, AutoPSEO can serve the pages exactly as your site does today. Take over as the site serves it is offered while hosting is on, for a content type with a path of its own, no learned look and no articles AutoPSEO serves: "AutoPSEO reads every page of this section, in every language, and serves it exactly as your site does. Do it while your site still serves the section. AutoPSEO writes no new article of it."

• The capture reads the section's pages from the scan, the section links found on captured pages and each page's language alternates, up to 3,000 pages.
• Each page is kept byte for byte, with its status and the headers that describe it, never a cookie. Redirects are kept as redirects. Where your site gives agents Markdown, that version is kept too, and so is your own 404 page for each language.
• Server errors, 401, 403 and 429 answers, bot checks, and pages AutoPSEO already serves are not kept.
• When it finishes, the type shows Served as captured, its waiting topics are parked, and no new article of it is written. Capture again refreshes it; a page your site now answers with 404 keeps its captured copy.

Serving hosted pages or a captured section on your own domain is not a switch in the app: it needs routes on your domain and is arranged with AutoPSEO. Contact us if you want it.