Fair questions

A growth report for a product business, bought once: from your URL it reads your site, the searches around it and the rivals on them, and writes every place growth is leaking with what to change, ranked.

The founder who ships the site: a SaaS, a store, a side project, an agency’s own product. It is written to someone who can make the changes, or hand them to an AI agent that will.

It is a report, not a dashboard. Tools show you figures and stop. The report reads the figures and says what they mean for you: which pages are shown and never clicked, who beats you on each search and what their page has, which pages to write and which to fold.

Eleven chapters in five parts: take searches back from rivals, climb what you already rank for, fix what costs you rankings, speed up your pages, show who stands behind the site, write what is missing, be named by the AIs, get linked, get listed, win the click, and turn visits into signups. Each chapter holds its sections, its figures and its findings.

It depends on the site. Every grouping offers up to twenty candidates and a planner judges them all, so a report holds roughly ten to twenty findings a chapter where the data supports them, and none where it does not. A finding is one change, never one page: a family of pages with the same problem is one finding.

A brief: what is happening with the figures behind it, what to change, the steps in order, the pages it touches, and how the next report will judge it. Written to be picked up by you or your agent, not read, translated and re-explained.

Yes, and differently. A site that ranks on almost nothing has no pages to fix; it has pages to build. The report reads what your product is, names its category and rivals, and writes the pages worth writing: the comparisons, the guides, the page families your rivals hold, the tools people search for.

About five minutes. The landscape, your site and your connected sources are read at once, and the findings are written by thirty-two writers in parallel. You get a mail when it lands; you do not have to stay on the page.

No. The report needs your URL and nothing else. Connect Search Console before it writes and every chapter holds your own impressions, clicks and positions. Connect PostHog and the growth report follows a search to the signup.

Nothing. Google is connected with the read-only Search Console scope, PostHog with the three read scopes the queries need. Porteur writes nowhere. The changes are made by you, or by your agent in your own repository, when you tell it to.

They should. Search Console withholds queries rare enough to identify who typed them, so a breakdown by query is only ever part of the total; on one property we measured, a fifth of the clicks. Porteur asks twice, once without the query for the totals and once with it for the queries, and the headline figures come from the first. Nothing in a report is estimated; a finding counted in pages or places says so.

From the searches themselves: the queries a site ranks on, the rivals on them, the volumes, the results pages and the AI answers are read from a search data provider, and your own figures from your Search Console and PostHog when they are connected.

Three ways. Copy for LLMs puts the whole report on the clipboard as Markdown, and you paste it into Claude Code, Cursor or ChatGPT. The skill teaches your agent to take the findings in order, in your own repository. The MCP server hands the agent the report, one finding whole, and answers its questions about a page, a query or a rival while it works.

No. Your agent already works in your repository; the report tells it what to change and where. Porteur never connects to a repository and never opens an issue or a pull request.

Any agent that reads Markdown works with Copy for LLMs. The skill is written for Claude Code, Cursor and Codex. The MCP server works with every client that speaks MCP, with a key you make in Settings.

The report is 99 €. The growth report, which adds your product analytics, is 199 €. Both are bought once, in euros, and nothing renews.

Neither. A report is bought once and it is yours: the page, the Markdown, the PDF, the kit. When you want to know what changed, you buy the next one from your own report page, written again from that day’s figures.

The difference: 100 €. A holder of the report pays the growth report with the 99 € already paid taken off.

Refunds are handled on request by Polar.sh, the merchant of record that took the payment and issued the invoice. Write to [email protected] with the report’s address and what went wrong.

Every search the site ranks on, every rival on those searches with the queries it wins, the searches of the category and who holds them, the sites that link to the rivals, the rivals’ own pages, and the results pages of the searches worth entering, with what Google’s AI answers quote.

Up to two hundred pages of your site: titles, descriptions, headings, word counts, canonicals, links between pages, structured data, authors and dates, whether the text is there without JavaScript, robots.txt, llms.txt, the sitemap, and how the key pages load on a phone.

Never. Every figure on a report is one that was read: your own from your accounts, the landscape’s from the provider, the pages’ from the crawl. A finding that rests on an estimate says so, and a section the check did not read says what the report reads for it.