A Page for Every Rule You Had to Look Up

Every rule you had to hunt down is a rule someone else is hunting down right now. The archive is the asset.

Last updated: October 29, 2026

You've looked up the same regulation twice. So has every host in your city. What separates you from them isn't knowledge, it's filing. One of you has a page, the other has a browser tab that'll close tonight.

Key Takeaways

• Your search history is an editorial calendar. The rules you had to dig out are the questions your market is typing into a search box this week.
• One page, one question. A page that answers five questions gets quoted for none of them.
• A rule without a place and a date is a rumour. Jurisdiction, authority and the day you checked it belong in the same paragraph as the number.
• Links do the work a sitemap can't. Each page should hand the reader to the next question in the order they'd ask it.
• Retire a page, don't delete it. A page marked superseded still answers "so what changed?", which is the question that brings people back.

Start from your own search history

Open your browser history and read the last ninety days of queries. Not the bookings, not the pricing experiments. The regulation ones. Most hosts find eight to fifteen of them, and they fall into three groups: what am I allowed to do, what does it cost, and what happens if I get it wrong.

The wording matters more than the count. You probably searched "short-term rental registration [your city]" and then, when that came back with a council page written for lawyers, you searched something narrower. "Do I need a permit for a two-bedroom." "Is the fee per unit or per bedroom." "When does the new rule start." Those narrower queries are the page titles. They're the exact sentences other hosts are typing, and they're the sentences an assistant will repeat when a guest asks.

Then go back to whatever you wrote down at the time. Most of us keep something: a note on the phone, a screenshot of the bylaw, an email from a clerk who actually answered. That note is the raw material, and it's better than anything you'd produce from memory in March. It has the article number, the person's name, the sentence that settled the argument.

There's a second reason to start here. The research cost is already paid. You spent an evening on the phone and two hours reading a PDF, and the only thing standing between that evening and a page is typing it out once, properly. Everything else on your content list is speculative. This is inventory.

One page, one question

A rule page has five parts, in this order: the question as the heading, the answer in the first two sentences, who it applies to, the authority plus the date you checked, and what the page doesn't cover.

The answer comes first because that's the part that gets quoted. "A one-bedroom unit needs its own registration; the licence runs with the unit, not with the owner." Two sentences, no preamble, no "in today's complex regulatory environment". If a reader has to reach paragraph four to find out whether they need a permit, the page has failed at the only job it had.

Then the scope. Who does this apply to, and who's exempt. A rule that covers buildings above a certain number of units is a different page from one that covers a whole city, and merging them produces a sentence that's true for nobody. Say which one you're answering.

Then the authority, named, with the date. Not "the council" but the department and the document, and the day you read it. If the wording changes next quarter, that date is what lets you fix the page instead of rewriting it from scratch.

Pricing questions need one more thing, because a rate is only a rate in context. The same Saturday can sit at four different amounts across four channels once each one applies its own rules, and hosts get asked about that gap constantly. Your calendar already shows each connected channel's source price and status for the same night, which is the evidence a page like this needs. localsbnb.com puts Airbnb, Booking.com, Agoda and Trip.com on one calendar, so the screenshot that explains "why your Saturday costs more here than there" takes a minute instead of an afternoon.

What stays off the page: the other four questions. If you find yourself writing "and also", you've found the next page.

The internal link that does the work

Rules come in sequences, and readers arrive in the middle of one. So write the sequence down and link along it. The shape most hosts end up with is four steps: what the rule requires, how you register or file, what it costs, and what happens if you're late.

Each page carries two or three links, and every one of them is a question the reader would ask next. "What the registration covers" links to "how to file the renewal", not to a homepage. Anchor text should be the question itself, since that's what a person scanning the page is looking for.

What doesn't work is the hub. A page called "everything you need to know about regulation" collects links and answers nothing, and it ends up competing with the pages listed under it. If you want an index, make it a short list of the questions with one line each, and keep it out of the way.

One more habit: link backwards as well as forwards. When you publish the fee page, go back to the registration page and add a line pointing to it. The reader who lands on the older page is the one who needs the newer one.

Retiring a page without losing it

Rules get amended, and the amendment is usually smaller than the coverage of it. When that happens, the instinct is to delete the page and write a new one. Don't. You'd throw away the only record of what the rule used to say, and that record is what makes the new page credible.

Keep the URL. Add a line at the top: superseded on a given date, replaced by this page. Leave the old answer visible underneath, with its own date stamp on it. A host who bookmarked it last year lands somewhere that explains itself instead of a 404, and a reader comparing two versions can see exactly which sentence moved.

Merge pages only when two of them answer the same question. That's the one case where a redirect is the honest move, and even then the merged page should carry a line saying what it absorbed.

The changelog is worth keeping as its own short page. "What changed this year" is the page people return to, and it's the one that shows a reader you've been at this longer than the last press release.

FAQ

How many pages do I need before this does anything?

Start with the ten you looked up last quarter and publish them before you plan the eleventh. Ten dated, specific pages on one city answer more real questions than forty general ones, and each new page gets easier because the links already exist.

Should these pages live on my own site or somewhere else?

On a domain you control. A page on someone else's platform inherits their rules about edits, and rule pages need edits. If you also publish a short version elsewhere, link back to the full page so the version with the date on it is the one people land on.

What if the rule changes twice in a year?

That's normal, and it's an argument for the changelog rather than against the archive. Update in place, keep the superseded wording visible, and add the date. Two changes in a year give you two pages of history, which is more useful to a reader than either version alone.

A rule page is a small, unglamorous thing: one question, one answer, one authority, one date. Ten of them turn an evening of research into something that keeps answering after you've closed the laptop. If the operational side of those questions is the part you'd rather not rebuild by hand, there's a shorter route. localsbnb.com keeps the four channels, their source prices and their statuses on a single calendar, so the facts you're citing stay a click away.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. What has to be registered, what it costs and when it must be renewed are set by local requirements that differ by place and change over time. Confirm the current wording with the competent authority before you publish anything as fact.