By hand
The city name swapped.
The same paragraph goes out with a different city in the first line. The hours, the team, and the offer are whatever the original page said. A customer in the second city can tell.
Content localizer
One article, every location.
The content localizer starts from one article you have already approved and writes a version for each location, using facts that belong to that location. Every variant waits for a person before it publishes. It was built for a client, and it is now being packaged. A multi-location owner is who it is for.
Two ways
Find-and-replace, or a version from that place.
With the system
Facts from that location.
Each version starts from the approved article and from a short file for that place: address, hours, services you actually offer there, and anything else you listed. If the file is thin, the draft is thin, and it waits.
Status
Built for a client, now being packaged.
We built this for one company. We are packaging it so another business can use the same motion. It is not a product you turn on from a pricing page.
How a version is made
The article, the place, then a person.
The source.
One article the business has approved. If that article is not approved, there is nothing to localize. The weekly publishing habit is where that source usually comes from.
The place file.
What is true at that location, written by you. The draft may use only that file plus the source article. It may not borrow a neighboring city’s hours to fill a hole.
The approval.
Each variant sits in the queue. A person who knows that location reads it. Publishing is a yes per variant, not a yes for the whole set.
The yes
Every variant is approved before it publishes.
One yes is not the set.
Approving the original article does not approve Dallas, or the second clinic, or the next store. Each version has its own yes.
A missing fact.
If the place file has no hours, the draft does not invent hours. The gap stays visible so the approver can add the fact or hold the page.
Who approves.
Someone who can say whether that location’s page is true. A central editor can do it if they have the file. A guess from a model is not the approval.
Duplicates
What the city and service pages hold.
Why the pages differ.
Each version is built from that location’s own facts. The point is a page a customer in that place can use, not a pile of near-copies aimed at a search result.
Before the page goes up.
A city or service page lists the address, the hours, and the services offered at that location. The owner compares those lines with the place file. If a fact is missing, the page stays in the queue until someone writes it in.
Thin locations.
A place with nothing but a city name does not get a page. Wait until you can say what you offer there. Shipping an empty version is how the set becomes noise.
Where it fits
Several locations, one publishing habit.
The source article.
Content and SEO is where the original piece gets approved and shipped. Localization starts after that yes.
Not the social caption.
Social publishing is the network queue. A city page is not a caption, and a caption approval does not cover the page.
The desks.
A trade with several cities, a shop with several stores, and a clinic with several offices can use the same motion. What they may say in public still differs.
Questions
Before a city page is a copy.
Do the location versions just swap the city name?
No. Each version is written from that location’s own facts: what you listed for the address, the hours, the services, and the notes that are true only there. The approved article is the spine. If the place file is empty, the draft does not borrow another city’s details to look finished. It waits.
Does each version need its own approval?
Yes. A yes on the original article is not a yes on every city. Each variant sits in the queue until a person who can check that location lets it publish. You can approve them on the same day. You cannot approve them as a bundle you have not read.
Will a set of city pages rank better?
More URLs are not a plan. A ranking or a citation is outside what this system offers. The reason to publish a location page is that a customer there can read something true about that place. If you cannot fill the facts, do not publish the page.
Was this built for someone already?
Yes. It was built for a client, and we are packaging it so the same motion can be set up for another business. The client’s name and numbers stay off the public write-up. The status is the useful part: the work exists, and the next setup is for the company in front of us.
Which site tools does it assume?
It does not assume a brand of site software. You need a place the approved article already lives, and a way to publish a page after a person says yes. If your setup makes that hard, the plan is where we say so. A tool becomes a requirement only after we have needed it for the setup.
The other cities
Tell us how location pages are made now.
A copied doc with the city swapped is a common start. We will say whether this is the first build.
Get your free Systems Plan