Our story

Being found used to be a skill. Now it moves every week.

Why we built mttr: what changed about being found online, where mttr comes from, and why the upkeep should not be yours to carry alone.

What changed

Six shifts anyone following AI has seen, in our own words, and what each means for a business that needs to be found.

  1. Search engines now write the answer themselves, above the links.

    A visitor can get what they need without ever clicking through. Being the page the answer is drawn from is the new first place.

  2. Assistants read the web live and cite a handful of sources.

    Five or six sites get named for a question. Everyone else is invisible, and is never told.

  3. People ask assistants what to buy, who to hire and where to go.

    The recommendation happens before anyone opens a browser tab. Your site is judged by a machine first.

  4. Agents now write code, open pull requests and ship changes on their own.

    The upkeep that used to need a developer and a free afternoon can be handed off, if something tells the agent exactly what to do.

  5. New models arrive every few weeks, each reading pages a little differently.

    What worked last quarter quietly stops working. Nobody sends a notice.

  6. Pages are being written by machines faster than people can read them.

    Clear, well formed, trustworthy pages stand out more than ever, and thin ones sink faster.

Where mttr comes from

It was not built in the abstract. It was built from the work.

16 yearsbuilding and running websites
18 monthsof AI research and development
7 monthson search and AI visibility, full time

We have built and run websites for a long time, our own and other people’s. For most of those years the work had a shape you could hold. Write good pages, make them fast, earn a few links, check where you rank. It took effort, but you always knew where you stood.

That shape is gone. Today a person asks an assistant a question and gets one answer back, put together from a handful of sites. If yours is one of them, you get the call. If it is not, you never find out you were in the running. There is no report for that, no rank to check. Just quiet.

And search did not stop mattering while that happened. So now there are two places a business needs to be found, and both shift week to week, by rules nobody publishes.

Then there is the upkeep. A page a teammate published on Friday with no description. A redirect that broke when the site was rebuilt. Forty service pages that say the same thing in slightly different words. A phone number nobody can tap. None of it is hard on its own. All of it together is a second job that nobody signed up for, and it is always the first thing to slip when the real work gets busy.

We watched good businesses, run by people who are excellent at what they do, lose ground to sites that were simply better formed. Not better companies. Better formed pages. That bothered us more than we can say.

So we built mttr. It reads your site the way search engines and assistants do, every page, and tells you plainly what is wrong and what to fix first, ranked by what each fix is worth. Then it hands those fixes to your agent, whichever one you use, and checks each one on your live site once it is done. When something new goes up that is not right, it shows up on the next read and goes straight back into the plan.

The day to day heavy lifting moves off your plate. You keep running your business. mttr keeps the pages honest and in shape, and your agent does the typing.

We will not promise you rankings, and we will not dress up a number. A score says your pages are well formed. It does not say an assistant cites you, and we will always tell you the difference. What we can promise is that you will see what is really there, and that the fixes will be the ones that matter.

We are early, and we are building this in the open, one read at a time. If something is wrong, or something is missing, tell us. It reaches the team, and we read every one.

v@subinternalFor the team at subinternal, the makers of mttr
718,994sites read
24,559,459pages read
44rules in the rulebook

A score says pages are well formed. It does not say an assistant cites the site.

What we hold to

  1. Honest figures

    A score says pages are well formed, never that an assistant cites a site. A sample is labelled a sample, and a feature not built says so.

  2. Your agent does the work

    mttr reads and ranks and checks. The changes to your site are made by the agent you already use, and you decide what ships.

  3. Careful on every site

    Public addresses only, its own crawler name, robots.txt obeyed, a few pages at a time. A site that keeps crawlers out is never read past its wishes.

  4. Nothing sold, nothing followed

    No advertising, no analytics script, no tracking cookie. What mttr keeps is never sold or shared, and a site’s owner can have it named by a code or removed.

Where we are going

  1. Being cited, measured

    Asking assistants the questions people really ask about a site’s line of work, and saying whether it is among their sources. Asking is built; showing it to you is not yet.

  2. Your sites in one place

    A signed-in view of every site you claimed: its score over time, its fixes, its campaigns and your agent’s work. Being designed now.

  3. Livecards

    Pages that play inside a post on X, from polls to a site’s own score. Making one works today on mttr; a home of its own is coming.

See where your site stands

Free, no sign-up, and a list of what to fix first.

Free, no sign-upScore, place and fixesAbout a minute

Free, no sign-up. About a minute.

Connect your agentHow it worksTalk to us