URLs that never change
A view that does not change its address cannot be indexed on its own. Every state that deserves traffic gets one crawlable URL and one canonical tag.
Technical SEO
for apps.
Search gets cheaper the longer you run it, and it is the channel most often broken by the way an app is built. Our engineers sit in the same team, so the fixes are implemented rather than listed in a report.
- Crawlability One address per page
- Rendering Server or build time, not script
- Links Hubs and spokes, nothing orphaned
- Reporting Indexed pages and real leads
Where apps lose search
Single-page apps and headless sites fail in predictable ways. These four cover almost every audit we open.
Content behind a script
A page whose text only exists after a bundle runs is a page a crawler may never read. We render on the server or at build time where it matters, then check what a crawler receives.
How we build the front endStatus codes and pagination
Missing status codes and pagination a crawler cannot follow quietly cap how much of a site gets read at all. Both are code fixes, so both ship in the same sprint.
Checked before releasePages written from a keyword list
We write from product knowledge instead. Each page answers one real question and links to the next step, which is what makes it worth crawling twice.
Content marketingHow a search engagement runs
The same order every time. You always know which stage you are in and what lands at the end of it.
See the full service map-
Crawl
We crawl the site the way a search engine does and record what it receives, not what the browser shows. The difference is usually the problem.
-
Render
The pages that matter move to server or build-time rendering. URLs, canonicals and status codes get fixed in the same pass, by the engineers who own the code.
-
Map
Hubs and spokes get drawn so nothing is orphaned and the pages that must rank collect the most internal links. Most sites lose more here than to weak content.
-
Report
Indexed pages, clicks by intent, and the leads search produced. Rankings are a lagging signal, so they are never the headline number.
The technical checklist
What we check on every site before anyone argues about keywords.
- Crawlable URLs, one address per page
- Correct canonical tags and status codes
- A sitemap built from real content, not typed by hand
- Structured data that matches the page
- Core Web Vitals treated as a budget, not a score
Before you ask
Answers as we would give them on a call.
Can you fix search on a single-page app?
Usually yes, and the fix is rendering rather than a plugin: the pages that need to rank move to the server or to build time. Because our own engineers do that work, it ships in the sprint we find it.
Do you report on rankings?
Not as the headline. Rankings are a lagging signal. We report indexed pages, clicks by intent and the leads search produced, set up the same way as the rest of your measurement.
How long before anything moves?
Technical fixes show up in crawl data first. Content and links take longer. We tell you which of the two applies to your site before you pay for either.
When is SEO the wrong first move?
If the product is not instrumented, start there. If your position is unclear, start with strategy and branding. We will say so rather than take the work.
Send us the site that is not being found
A URL is enough to start. We reply with what a crawler currently sees, the first three things we would change, and what they cost.