You can rewrite a whole website with ChatGPT, page by page, but the method decides whether it helps or hurts. Pasting your live URL is the common first try, and it is where most rewrites go wrong: the model gets a page buried in theme markup and returns half the content or invents the rest. The reliable approach is to export each page as clean Markdown, rewrite that with a clear brief, and publish the new copy on the same URL, since rankings follow the content and the address, not the wording. WPBuildAI exports your whole site as clean Markdown and rebuilds it, so a model-assisted rewrite ships on a fast site with every redirect mapped.
Before rewriting wholesale, find out which pages already earn citations: Seer Interactive’s 2026 analysis of 2.43 billion impressions found pages cited in an AI Overview running at roughly 2.1 percent click-through against 0.9 percent for uncited pages, so a rewrite that quietly deletes the passage an engine was quoting costs more than it gains.
Why pasting a URL produces a poor rewrite
A WordPress page is mostly not content. The text sits inside theme containers, widget output, inline scripts, and stylesheets, and a URL fetch has to wade through all of it. The 2024 Web Almanac shows how much markup and script a typical page ships before any real content, which is exactly the noise that crowds out a model’s view of the page and burns its context window. Pages that depend on JavaScript to render are worse, the rendering gap Google describes in its JavaScript SEO basics, because the words may not exist yet when the fetch reads them. Export the page to Markdown and the model sees only the headings, sentences, and links, which is what it can actually rewrite.
What a rewrite should change, and what it must not
The goal is to sharpen, not to spin. Research on what AI engines surface, the Generative Engine Optimization study, found that content with clear structure, defined facts, and concrete specifics is quoted far more often than generic prose. So a rewrite that helps clarifies the answer, tightens the structure, and keeps the real facts, entities, and internal links. A rewrite that hurts pads a thin page with filler or strips out the specifics that earned its rankings. Before rewriting a page, decide which facts, figures, and links are load-bearing and tell the model to preserve them.
How to brief the model so the output is not generic
Generic output is almost always a prompt problem, not a model problem. Give ChatGPT three things for each page: the page’s real content as Markdown, a short description of who it is for and what job it does, and the facts or figures it must not change. Ask it to improve clarity and structure rather than reinvent the page. With real material and a tight brief, the rewrite reads like a sharper version of your page; with a vague prompt and no source content, it reads like every other AI page. The difference is input, which is why the clean export matters as much for a rewrite as it does for analysis.
Doing it across a whole site
A site-wide rewrite is the same per-page process, repeated with discipline:
- Export every page as clean Markdown, with the URL noted at the top.
- Rewrite page by page, feeding the Markdown plus the brief, and reviewing each result.
- Keep the URL and the ranking headings, improving the copy rather than the address.
- Rebuild on a clean site and map every old URL to a 301, the same discipline as moving WordPress blog posts without losing rankings.
- Resubmit the sitemap and watch Search Console for a month.
Working from a per-page export, rather than fetching live URLs, is what keeps the rewrite faithful at scale, and it is the same export described in turning your whole website into ChatGPT-ready Markdown.
Protecting rankings through the rewrite
Rankings attach to the content and the URL, so the safest rewrite changes the words and leaves the addresses alone. Keep the slugs, carry over titles and meta descriptions, and preserve the internal links, then 301 anything that genuinely has to move, following Google’s site move guidance. A rewrite that ships on the same URLs with better content usually holds or improves rankings, because the page is more useful to both readers and the AI engines that quote it, the connection drawn in getting your website cited by AI search.
A realistic workflow for a 50-page site
Across fifty pages, the order of operations keeps the project from sprawling. Start by exporting all fifty as clean Markdown and sorting them by value, so the pages that earn traffic get the most attention. Group them by type, because product pages, guides, and policy pages each need a different brief, and a shared brief per group keeps the voice consistent. Rewrite a small batch, review the results against the originals, and adjust the brief before running the rest, rather than rewriting all fifty and discovering the same issue fifty times.
Hold the structure steady while the words change. Keep the slugs, the headings that rank, and the internal links, so the only thing moving is the prose. A spreadsheet that tracks each page’s URL, its status, and whether its facts were verified turns a vague project into a checklist you can finish. The work is repetitive, but it is predictable, which is what makes it safe to do at scale.
How to review the rewrite before it ships
A model’s draft is a starting point, not a finished page, so build in a review step. Check three things on every rewritten page: the facts and figures match the original or a verified source, the meaning was sharpened rather than changed, and nothing was quietly dropped, like a key detail or an internal link. Read the opening aloud; if it answers the question in the first two sentences and sounds like a person wrote it, it is on track. Watch for the model’s habits, the confident filler sentence, the vague adjective, the repeated transition, and cut them.
For anything where accuracy carries weight, prices, specifications, medical or legal points, treat the rewrite as a first pass that a human with the facts has to approve. The model is good at clarity and structure and unreliable on specifics it was not given, so the review is where you catch the difference. A page that reads well and states something untrue is worse than the original, which is the failure the review exists to prevent.
When a full AI rewrite is the wrong call
A whole-site rewrite is not always warranted. Pages that already rank well and read clearly are better left alone than risked for marginal polish, since a rewrite always carries some chance of losing what worked. Highly technical, legal, or regulated content needs expert review rather than a model’s first draft. And a rewrite cannot fix a structural problem like a slow site or broken information architecture; those need a rebuild, not new words. Use an AI rewrite where clarity and consistency are the real gaps, and leave it where the page is already doing its job.
How to write the brief that drives the rewrite
The brief is where a rewrite is won or lost, so it is worth treating as a real document rather than an afterthought. A useful brief for each group of pages names four things: who the reader is and what they are trying to do, the job this page does in their decision, the facts and figures that must not change, and the tone to write in. It also says what to keep, the headings, the internal links, the key terms you rank for, so the model improves the page rather than reinventing it.
A short example makes the difference visible. A weak prompt is “rewrite this page to be better,” which invites generic filler. A strong brief is “rewrite this returns-policy page for customers checking whether they can return an opened item; keep the 30-day window, the exception for hygiene products, and the link to the contact page; plain, reassuring tone; lead with the direct answer.” The second produces a page that is sharper and still true, because the model had the constraints it needed. The clean content plus a tight brief is the whole recipe, which is why the export matters as much as the model.
Measuring whether the rewrite helped
A rewrite is a change, so check that it was an improvement rather than assuming it. After the new pages are live, watch Search Console for the rewritten URLs over the following weeks: rankings and impressions should hold or rise, not fall. A drop on a specific page is a signal to compare the new version against the old and check whether a ranking heading, a key term, or an internal link was lost in the rewrite. Engagement signals like time on page and conversions tell you whether readers find the new copy more useful, which is the real goal beyond rankings.
Keep the originals until you are confident, so you can restore a page that underperformed. Treating the rewrite as a measured change with a rollback option, rather than a one-way switch, is what makes it safe to do across a whole site. The pages that improve, you keep; the rare page that regresses, you revert and rework with a better brief.
The rewrite and a migration are one job
The clean, per-page export that feeds the rewrite is the same inventory a migration runs on, so doing both at once is efficient rather than double work. Rewrite the content, rebuild on a faster platform, keep the slugs, and map every URL, and you end up with sharper copy on a faster site that kept its rankings. If exporting, rewriting, and redirecting a whole site by hand is more than you want to manage, WPBuildAI runs the export, the rebuild, and the redirect map together; send your site URL for a fixed quote.
Keeping one voice across a rewritten site
A risk of rewriting page by page is that the site ends up sounding like several different writers, because each prompt nudges the tone a little differently. The fix is a short style note that travels with every brief: the reading level, whether you address the reader directly, the words and phrases you favour and the ones you avoid, and a sentence or two of example copy in your voice. Feeding that to the model on every page keeps the rewrite consistent, so the finished site reads as one person wrote it rather than a committee.
Consistency also covers the small mechanical choices that betray machine writing when they drift: how you format lists, whether headings are questions or statements, how you handle product names and numbers. Decide those once, put them in the style note, and check them in review. A rewritten site that holds one clear voice reads as a deliberate refresh; one that wobbles between registers reads as exactly what it is, a batch of separate prompts, which undercuts the trust the rewrite was meant to build. If you have an existing brand voice guide, hand it to the model alongside the page; if you do not, write the short version once and reuse it, because the half hour it takes pays back across every page you touch.
Key points to remember
ChatGPT can rewrite a whole website page by page, but feed it clean Markdown rather than a live URL, give it the real content and a tight brief, and publish on the same URLs. Keep the facts, headings, and internal links, improve the clarity, and 301 anything that changes. Leave pages that already work, get expert review for regulated content, and treat a rewrite as a content fix, not a substitute for a rebuild. Done this way, an AI-assisted rewrite is an upgrade rather than a traffic reset, and pairing it with a clean rebuild lets you sharpen the copy and speed up the site in a single, careful pass. If you would rather not export, rewrite, and redirect a whole site by hand, WPBuildAI runs the export and the redirect map together; send your site URL for a fixed quote.
Not affiliated with OpenAI, WordPress, or Lovable.