Always-on content

Every item in the queue names the question it answers, the customer stage it serves, the page that will own it, and the source behind any claim. Items without a question do not enter the queue. That single rule prevents most of the thin pages a mover site accumulates: a page per suburb, a page per synonym, a page per holiday.

The queue is ordered, not dated. Order comes from the calendar of real demand (chapter 12) and from dependencies: a service page before the city pages that link to it, tracking before reporting.

Every page clears the same checks before it ships:

• The answer is in the first sentence, before any context.
• Numbers, prices and timeframes come from your own operation or from an official source, never from another website.
• Regulatory claims link to the document that states them.
• The page answers a question a customer asked, in the words they used.
• The page is not a template with the place name swapped; it has information specific to that place or service.
• Internal links connect it to the service hub and to the pages above and below it in the customer's decision.

The doorway-page test in chapter 5 is the one that matters most here: if the page would be useless to a customer who arrived from anywhere other than a search engine, it should not exist.

A page about a rule has a shelf life set by the rule. When you review, open the cited document, confirm the claim still matches, and check that the link resolves. A page about your own operation is reviewed against what the crews and the office actually do now.

Review in small batches on a fixed cycle rather than rewriting everything at once. A batch you can finish and verify is worth more than a sweep you abandon.

Two pages competing for the same question split their own signals and confuse readers. When the research log shows two pages answering one question, keep the stronger URL, fold the useful material into it, and send the old address to the survivor with a permanent redirect.

A retired page leaves the sitemap, the internal links and the navigation in the same change. An orphaned redirect is a smaller problem than an orphaned page, but both are untidy.

It does not promise rankings, traffic or bookings. It does not publish city pages in bulk, and it does not automate writing at a scale no one can review. If a page cannot be checked by a person who knows the business, it is not ready.