Build log
Rank and rent means building a local service website, getting it to rank, and renting it to one local business that gets every enquiry. I'm doing it with a crew of AI agents. This is what the build actually looked like for my first two sites, medfordseptic.com and roanoketreeremoval.com. Neither has a renter yet and revenue is $0. Sites take months to rank, and some never do, so treat this as a build guide, not a promise.
Step 1: pick the market with evidence
The Market Researcher agent looks at a trade and a city together. It checks who ranks today and writes down the weak spots it can see:
- Thin one-page template sites in the top results
- Gmail or Hotmail contact addresses on business sites
- No dedicated service pages or city pages
- Typos and leftover template text
- Directories ranking among the businesses
- The strongest competitor based in another town
It also writes down the red flags. When national franchises own the page, the market gets rejected, however good the rest looks. One of my candidate markets was dropped for exactly that.
I didn't pay for a keyword tool. The agent used free signals such as search suggestions, and every demand note is labelled as an estimate. Watch for place names that exist in several states. Always add the state to the query.
Step 2: check the domain before you get attached
The agent checks availability with an RDAP lookup and records the result with a date. Buying the domain is gated, like any spend. A domain at cost was about $10.46 a year when I priced it.
Step 3: write the brief as data
The site builder is a Python script. A JSON brief goes in, a folder of plain HTML comes out. The brief lists the business type, city, services, service areas, guide topics and FAQs. Keeping it as data means you can fix a fact once and rebuild every page, and you can diff one version against the next.
Step 4: generate the pages
Each rank-and-rent site came out at 32 pages:
- Home
- A services index plus 5 or 6 service pages
- An areas index plus 12 area pages
- A guides index plus 6 or 7 guides
- A cost guide, an FAQ, an About page and a Contact page
Measured on body text only, without header, navigation, footer or scripts, that's about 22,100 words on the septic site and about 20,300 on the tree site. The sites launched at 18 pages and grew to 32 the same day.
The trap here is thin, near-duplicate area pages. Twelve area pages that only swap the town name help nobody. Each area page needs something specific to that place: which parts of the service area it covers, local conditions that change the job, the questions people there actually ask. If the agent can't find anything specific, the page shouldn't exist.
Step 5: keep a sources file
Every factual claim on the site goes into a sources file with a link and the date it was checked. Facts that can't be verified are hedged in the copy or left out. One example: the county listed two different phone numbers for the same office, so my site lists neither. A local site lives on trust, and one wrong permit fee or phone number costs more than the page is worth.
The same rule covers the business side. A referral site has to say plainly that it's a referral service, not a contractor. No invented licences, reviews or years in business.
Step 6: build, test, zip, then deploy by hand
The agent builds the site, checks every internal link, writes the sitemap and zips it. Deploying is gated, so I push it live myself on Cloudflare Pages. Before calling a site done I check that the live sitemap matches the local copy. On both sites it matches byte for byte.
A short launch checklist catches most mistakes: a favicon on every page, a real 404 page, a sitemap with the final URLs and a robots.txt pointing at it, one H1 per page, a privacy page in the footer, and no placeholder text left in the files.
Step 7: the phone number problem
A rank-and-rent site needs a phone number before it has a renter. My first version showed a visible placeholder on the call button, because I'd rather show a gap than a fake number. Both sites now have a real tracking number with voicemail sent to email, so any call that comes in before there's a renter is logged and answered.
Step 8: measure before you pitch
Nobody rents a site with no traffic. I won't contact a single potential renter until I can show Search Console impressions or logged calls. As of this week:
- Rank-and-rent sites live: 2, at 32 pages each
- Search Console impressions and clicks: none recorded yet
- Renters: 0
- Revenue: $0
While the sites age, I work on the agency side, auditing local businesses and sending one-page reports. That keeps the agents busy on work that can pay sooner, and it doesn't depend on rankings.
Common mistakes to avoid
- Launching thin and planning to fix it later. Mine launched at 18 pages and I spent the same evening getting to 32. Plan the full page list in the brief from the start.
- Copying a competitor's structure word for word. Use their gaps, not their text. The weak spots the researcher found are a to-do list, not a template.
- Using a real company's name or logo. A rank-and-rent site is your brand until a renter takes it on. Pick a plain descriptive name and domain.
- Forgetting the boring pages. A privacy page, a contact page and an honest About page make a local site look like a real operation, because it is one.
- Pitching renters on page count. Owners care about calls, not words. Wait until you have impressions or logged calls to show.
How long the build took
The research, brief, generation and checks for both sites fit into a single working day for the agents, with me approving purchases and the deploy along the way. The slow part comes afterwards. Search engines take months to decide what a new site is worth, and nothing the agents do on day one changes that. Plan for the waiting, and have something else for the crew to work on while you wait.
A brief template you can copy
The JSON brief for each site holds the same handful of fields:
- Trade and the exact service names people search for
- Main city and state, plus the list of service areas
- Guide topics, each one tied to a question real customers ask
- Cost-guide line items, each with a source and a date
- FAQ questions and short answers, sourced where they contain facts
- The referral disclosure text and the contact method
Fill those in well and the generator does the rest. Fill them in badly and you get 32 pages of filler, quickly.
What the agents did and what I did
The agents did the market research, the competitor notes, the domain check, the brief, the page generation, the sources file and the link checks. I picked between the shortlisted markets, approved the domain purchase, read the pages and pushed the deploy. That split is what makes it workable: the agents produce a lot, and nothing reaches the public until a person has looked at it.