How to Publish AI Visibility Fixes to Your CMS Without a Developer

Step 1: Start From a Question You Are Losing

A page earns its place by winning a question, so pick the question before the page. Choose one where AI names your rivals and leaves you out, and check it twice: in our tracking, a brand left out of two runs in a row came back on the next run only 3.4% of the time, so a gap seen twice is real. Write down who is named instead and which pages are cited. Our one-question workflow covers this part in full; this post picks up where the writing starts.

Step 2: Draft in the Format AI Cites

Open the pages AI cites for the question and note their format. Across citations to content pages in our study, ranked lists drew 35.7% and how-to guides 9.7%, but the format that wins changes from question to question, so match the pages cited for yours.

Brief before you draft

Write the question, the format and the facts the page must carry before any draft exists. Our brief template has ten fields for it, so the draft starts from what the page has to prove rather than from a keyword.

If the page already exists

Rework it rather than publishing a second page on the same question. The changes are text you paste into the page you have, which needs no developer either; our refresh checklist covers what to change.

Step 3: Edit Before Anything Goes Live

Drafting with AI is not the problem. Google's guidance says appropriate use of AI or automation is not against its guidelines. What its spam policies target is many pages made mainly to manipulate rankings, and a pipeline that publishes every draft unread leaves no one to check that each page adds something. The edit is also where the page gets what AI cannot invent:

• The direct answer to the question, in the first paragraph.
• Facts only you have: your pricing, your limits, real examples and first-hand steps.
• A source for every figure, and nothing you would not say to a buyer.
• Your product named where it fits the answer, and nowhere else.

Step 4: Connect Your CMS Once

How the page reaches your site depends on what your site runs on. For most sites built on a CMS the answer is WordPress: it runs 39.6% of all websites and 58.3% of those whose CMS is known, according to W3Techs.

WordPress: one application password, no plugin

Since WordPress 5.6, application passwords let another app sign in to your site's REST API with a password made just for it, never your own. You create one on your WordPress profile and paste it into the tool with your site address and username. Nothing is installed on the site. Two things can block it: a WordPress.com plan that does not offer application passwords, and a security plugin that turns off the REST API or application passwords. Check both before you start; our WordPress setup guide lists what the connection needs.

Use an account whose role can publish. In WordPress's roles, an Author can publish their own posts and a Contributor cannot. One more detail decides whether charts survive: only Administrators and Editors hold the unfiltered_html permission on a single site (only super admins on a multisite network), and as our publishing guide notes, WordPress removes inline charts from posts saved by anyone else.

Every other CMS: paste clean HTML or Markdown

Without a direct connection, the page still needs no developer if your editor accepts HTML or Markdown:

If the post has charts and your site renders Markdown, use the HTML route: Markdown keeps charts as code blocks, which most renderers show as code.

Step 5: Send a Draft, Then Publish

Send the page to your CMS as a draft first and read it in the CMS's own preview, where your theme, fonts and widths apply. Check that charts and tables came through, that links open where they should, and that the slug and excerpt read the way you want them in search results. Then publish from the CMS, or switch the draft to live.

Update the same post, never a second one

When you change the page later, update the post you already published rather than sending a new copy. A second copy leaves two pages answering one question, and readers, search engines and AI engines have to pick between them.

Step 6: Add the Schema Where It Survives

JSON-LD schema belongs in a script tag, and WordPress strips script tags from posts saved by accounts without unfiltered_html, the same accounts that lose charts. So keep the schema out of the post body and add it where it will stay: your theme's page head, or the structured-data field of the SEO tool your site already uses. Keep expectations level, too. Schema confirms what the visible page says; our schema guide covers why it is not, on its own, what gets a page cited.

Step 7: Re-Ask the Question and Count

Publishing is the middle of the job. Note which engines name you on the question the day the page goes live, then ask it again every week. Take an early read after 2 weekly runs and a verdict after 4, because a new page takes time to be crawled and picked up. An answer that names you on two runs in a row is a win; a single run is a maybe, since a first mention held to the next run only 54.3% of the time. Our guide to telling whether a change worked has the full protocol, and our AI search content plan puts this step inside a quarter.

The Pre-Publish Checklist

One per page. Tick the first block before the draft goes to your CMS, the second before it goes live, and the third the day it does.

BEFORE THE POST GOES LIVE

THE PAGE
[ ] It answers one tracked question, in the first paragraph
[ ] It is in the format AI cites for that question (ranked list, how-to, ...)
[ ] Every figure has a source you could show a buyer
[ ] It carries facts only you have: pricing, limits, real examples
[ ] Slug and excerpt read the way you want them in search results

IN THE CMS
[ ] Sent as a draft and read in the CMS preview
[ ] Charts came through (or show as tables of their numbers)
[ ] Links open where they should
[ ] JSON-LD added to the page head or your SEO tool

THE COUNT
[ ] Baseline noted: which engines name you on the question today
[ ] Early read after 2 weekly runs, verdict after 4
[ ] One or two untouched questions kept as a control

How Ranqo Does It, With No Developer

We built Ranqo to run these seven steps from one place, from the question you lose to the page on your site.

• Steps 1 and 2. Ranqo asks your tracked questions every week. When you generate ideas, Blog Ideas turns the questions your latest run left you out of into article ideas, each with who AI names instead and the format of the pages it cites. Generate Blog drafts the post from the idea at the length you pick. For a page you already publish, the Content Optimizer returns before-and-after changes to copy in.
• Steps 4 and 5. Connect WordPress once with an application password; Ranqo signs in to test it before saving anything. Then publish each post as a draft or live, with the slug and excerpt prefilled. Publishing again updates the same WordPress post in place, and Ranqo asks first if the post was changed in WordPress since. If the connected account cannot keep charts, Ranqo sends them as tables of their numbers. Starter includes 1 WordPress connection and 5 posts a month, and publishing itself counts toward no monthly limit. On any other CMS, export the post as HTML, Markdown or a bundle.
• Step 6. Every post comes with its JSON-LD, kept out of the body on purpose: copy it from the post page, or take it from the HTML page and bundle exports.
• Step 7. The weekly runs keep asking the question after you publish, and each question's insights page keeps every answer, so the count arrives without anyone re-checking by hand.