PRAIRIEMARK
Certified sites · Rapid City

A certified website for a Rapid City shop.

Built to the public code for web pages, inspected at launch point by point, and handed over with its certificate, its record and the whole site in your name — that is what certified means here, and this page itemizes it.

Start today
What a certified site is, in one place

Prairie Mark builds certified websites for Rapid City shops: built to the public code for web pages, inspected at launch point by point, and handed over with the certificate, the itemized record and a copy of the whole site in the owner's name.

What a certified site is, in one place Prairie Mark builds certified websites for Rapid City shops: built to the public code for web pages, inspected at launch point by point, and handed over with the certificate, the itemized record and a copy of the whole site in the owner's name. The site carries the shop's own record — who you are, where you are, how to reach you, when you're open, what you do and what you will not do — in a form a customer and an AI both read the same way, confirmed by the owner before it ships, and every figure for it is printed on the pricing page.
Measured · Certified · Delivered

What certified means.

  • Measured

    A scored baseline before anything ships — speed, reach, search health. Progress is a number, not a feeling.

  • Certified

    Launch is an inspection, pass or fail. Your certificate is public, signed, and dated.

  • Delivered

    An itemized statement of everything that went in — a record you can hold me to.

  • Structure. Clean bones, checked against the public code for web pages, and a person reads every page before it ships.
  • Answers. A machine handed the finished page comes back with your shop, not a guess, because the record is on the page in the form it reads.
  • Reach. Fast on a phone at a job site, found by the shop's name and the town, and the score is one you can read yourself.
  • Record. Every point that passed is written down, signed and dated, and the record goes to you with the site.

See the numbers

The inspection, point by point Structure — measured: every page's markup is read against the public standard, one page at a time, and then by a person; passes: no error on any page, and the read-through done. Answers — measured: the finished page is handed to an answering AI with the shop's name and nothing else; passes: it comes back with the shop, the town and the work, and nothing made up. Reach — measured: the page's weight and its load on a phone over a slow connection, and whether the shop's name and town sit where a search reads them; passes: the score reads out where the owner can see it, and the page loads without a wait. Record — measured: the six record fields on the page against what the owner confirmed; passes: every field present, matching, and carrying the date of the owner's confirmation. The domain: registered in your name, with the login in your hands from the first day, so the address belongs to the shop and not to the builder. The words and pictures: everything written for the site and every picture on it is yours, in the files, in a plain form you can hand to the next person. The zip: the whole site as files and folders, handed over at the handover and again on request, and it runs on any host; the certificate names the build it was taken from. The certificate: one page, public, signed and dated, naming the build, the date, every point inspected and what it read; a filled one appears on this site only when a Rapid City build has published it.
The record

What the site has to have on it.

  • Who you are. The shop's name, the owner's name, and what the shop is — the same on the page as on the sign.
  • Where you are. The town, the county, and the ground you cover — so a question asked from Rapid City gets a Rapid City answer.
  • How to reach you. The phone and the email, printed once and the same everywhere a machine looks.
  • When you're open. The hours as you keep them, and the day they were last confirmed.
  • What you do. The work, in the words a customer uses when they call about it.
  • What you will not do. The jobs you turn away, said plainly, so nobody is sent to you for the wrong thing.

Confirmed by you. Every field above goes up only after you have read it and said it is right, and the date you said so is on the page.

What an AI reads from, and why the record beats an argument What it reads from: an answering AI does not read a page the way a customer does; it takes the parts it can name — a business, a place, a phone, hours, a list of services, a date — and builds its answer from those. A page that carries them in a form it can name gets read right; a page that carries them somewhere in a paragraph gets read approximately. Why the record beats the argument: where a field is missing the AI does not leave a gap, it fills one — a name from an old listing, a town from a similar shop, a service you do not offer — and says it in the same sure voice as the true parts. A record on the page, confirmed by the owner and dated, is the one thing that stops the guess; the fields above are that record. Where it lives: once on the page as the six fields, and once more in the machine's own copy of the site (the page's data block and llms.txt), both rendered from the same source so they cannot disagree; you confirm it once, and the date you did travels with every copy.
What you get

What you get.

Built to code.
Clean bones underneath, and a person reads every page before it ships. The code is the public standard for web pages; it has been there for years, and a site is either built to it or it is not.
Mobile first.
Built for the phone in a hand at a job site, then for the desk. Every page is laid out for the small screen first, and the tap that calls you is on it.
Fast, and measured when it's done.
The reading goes on your certificate, where you can check it the same as I can. The page's weight and its load on a phone are measured on the finished site, not promised ahead of it.
You own it.
The domain, the words, the pictures — and a zip of the whole site, yours to take anywhere. The domain is registered in your name, and the zip runs on any host, so leaving is a decision and not a fight.
Edits by the one who built it.
Two changes a month by my hand, inside a scope you read before you sign. A fix to my own mistake never counts and is done free, and the scope is printed beside the price so nothing about an edit is a surprise.
Rapid City Built.
One shop in town, doing the work here. The person who takes your call, builds the site and picks up afterward is one person, and I live here.
The speed

How fast, and how you can check.

The speed score of a finished page, read on a phone Unmeasured The number prints here when the first Rapid City build reads out.

Most of a build is work that has been done a thousand times over. I built the jig once, so that part comes out right every time, and the days that are left go to what is yours. Fast is what a proven system looks like from the outside, and the inspection does not care how quick the build was.

A page built by hand loads quicker than one stacked out of drag-and-drop parts, and the score says so where you can read it.

The jig, the limit, and how to read the score yourself The jig: the part of a build that is the same for every shop — the structure, the record fields, the inspection — is built once, checked once, and reused, so it comes out right each time and the hours go to the part that is yours; that is what fast is here, and it is the same reason the score holds. The limit: no Rapid City build has been timed end to end yet, so the length of one is class language — days — until a repeatable build reads out; a number goes in the tile when it is measured and not before, and the checkpoints under how it goes are the days the build turns to you, not a promise of the whole. How to read the score yourself: open the finished page on your phone; the certificate names the reading and the day it was taken, and the same read runs on any public page-speed tool against any site, so the number it gives you is the number I get.
How it works

How it goes.

  1. First, a talk — I learn how your shop runs and how folks find you now.

    A free video chat: you answer a handful of questions about the shop, the towns you work in and the jobs you turn away, and that is the record's first draft.

  2. Then I build it — days, not weeks, and you see it before it ships.

    You see the site twice before launch, once with the core pages up and once with all of them, and each time you send back what to change; the inspection runs last, and the site ships when every point passes.

  3. Then you've got a front door that works — one a customer can use and a machine can read.

    The handover is the certificate, the itemized record and the whole site as files, with the domain in your name; from there the changes come by my hand inside the scope you signed.

Your part is one talk and a handful of questions answered. It is not a project you have to run.

The two checkpoints and the build's ten changes Day 5: the core pages are up — the front page, the services, the contact — and you read them; what you send back is spent from the build's ten changes, and a wrong number or a misspelled town never counts. Day 8: every page is up, the record fields are filled from what you confirmed, and you read the whole site once more; the rest of the ten are spent here, and the inspection runs after your last word. What you do at each: read it on your phone, tell me what is wrong or missing, and confirm the record — the fields are yours to say yes to, and the date you do goes on the page; nothing about the build asks more of your time than that.
The rung aboveAdd it when you're ready

Once the site is up, there is a rung above it: an AI that answers the phone when you cannot and books the job into your calendar. It needs the record this page describes, because that is where it learns your shop, so the site comes first and the AI is never sold without one. Nothing here asks you to want it yet.

Never miss another job

The answers

Straight answers about the build.

How long does it take?
Days, not weeks — a class, not a number I have timed yet.
What counts as an edit?
One change to an existing page: words, a price, a photo, a town.
Can my own AI change the site?
Yes, inside the post types approved for your site, without limit.

All the answers

The door

Let's talk.

If what you read here is what you want built, pick a time. I will ask how your shop runs, tell you straight what a site built to code and certified would and would not change for it, and the first invoice is the build itself.

Set up a time