We publish two SEO and GEO projects. Next to each figure we say where it came from and how we counted it. Where there was no measurement, we write that there was none instead of a growth percentage we could not defend.
Both without the client's name, because we publish names only after written consent. What is left is the part that has value for a reader: what was wrong, what exactly we did, and what could be verified afterwards.
A case study on the Neurise site itself. Content had outgrown both the funnel and the measurement: 238 HTML files, a contact form on four of them, and 112 of those 238 pages outside the sitemaps, measured as the difference between the files on disk and the addresses the sitemaps list. The baseline was counted before any repair, with the counting method next to every figure.
Read the case study on our own site (in Polish)A case study with no client name. A modern site assembled in the browser, where the search engine crawler received a practically empty document. The technical layer was repaired without rewriting the site, and the limits of what could be measured are stated plainly. The 38 characters are the size of the raw HTML the crawler received for that page, before any JavaScript ran.
Read the esoteric-sector case study (in Polish)Both case studies are published in Polish only. They are long technical write-ups, and translating them well costs more than it would return at this stage of the English rollout. If you want either of them walked through in English, ask and we will do it over a call or by e-mail.
Which is why a few things that are standard in agency case studies are deliberately missing here.
The same rule applies to monthly reports. If there is a number in the report, the tool and the period it came from stand next to it.
We do not guess. Every project runs through the same process, in which measurement is set up first and promises about measurable effects come after.
We check what the crawler actually sees in the raw HTML and connect the measurement. Without this step no effect can be proven later.
Titles, descriptions, sitemap, robots file, llms.txt, canonical addresses, and removal from the index of pages that will never sell anything.
Answers to the questions buyers really ask, plus structured data so that a search engine and an AI model know who this is and what is on offer.
We report what counts and put the tool, the period and the counting method next to every figure. Including the periods where the figure came out badly.
| Stage | What happens on our side |
|---|---|
| Audit and plan | Diagnosis of the site and an implementation plan broken into steps, each with an acceptance criterion, an owner and a risk. The plan is closed before the first change to the code. |
| Technical rollout | Changes reach production as merge requests in the repository, with no downtime and no change to how the site looks. Every step is signed off on the live site. |
| The stage that depends on you | Access to the domain for measurement, plus material about the team and the offer. This is the most common reason a deadline slips, because it is not a part we can close ourselves. |
| Content and authority | Publishing answers to buying questions and building credibility in the places that search engines and AI models actually cite. |
| Reporting | On a cycle, with the measurement method next to every number and a list of the things that could not be measured in that period. |
The conclusion we reach most often: the technical work itself takes days, not months. Months go on waiting for access and materials.
The figures below come from public studies of search result click behaviour. They are market data about how people behave, not results of any Neurise client.
The full methodology, the list of every source and a note on which coefficients are our assumption rather than a measurement sit in the calculator of the cost of being invisible in Google and AI (in Polish). It runs in PLN on Polish market rates, so read it as a worked method rather than as your own figure.
Each stage of the work above has its own page in English.
A free SEO and GEO audit in 5 working days. We check what the crawler sees, whether AI models have anything solid to quote you from, and where you lose contact with the buyer.
NEURISE sp. z o.o., ul. Karola Szymanowskiego 6/10, 99-300 Kutno, Poland. KRS 0001208946, VAT ID PL7752678033.
E-mail: seo@neurise.io
Phone: +48 509 919 101