Neurise / Technical SEO

Technical SEO: crawling, indexing and Core Web Vitals

The best content and the strongest links do nothing if Google cannot fetch your pages, keep them in the index and render them quickly. We work on the layer underneath, then implement the fixes and show the difference in Search Console. Not a PDF and a handshake.

What technical SEO actually is

Technical SEO means adapting the code, structure and performance of a site to what search engines need from it. It rests on three things: crawling (whether Googlebot reaches your pages), indexing (whether those pages end up in the index) and performance (whether they load fast and stay stable while they load).

When crawl budget is burned on duplicates and 404s, and the page needs six seconds to show anything, even a genuinely good article has no chance of competing. That is why we start here. Every unit of budget you spend afterwards on content and links then lands on a foundation that works. The full picture of what we do is on the services page.

What the service covers

Core Web Vitals: what counts as a good score

Core Web Vitals are the three metrics Google uses to measure real user experience. According to Google's own documentation, a good result means LCP under 2.5 seconds (how fast the main content appears), INP under 200 milliseconds (how quickly the page responds to interaction) and CLS under 0.1 (how much the layout jumps while loading). Worth knowing: INP replaced the older FID metric, and plenty of agencies are still optimising for a number Google no longer reports.

How we get to green

We work on field data from the Chrome User Experience Report, not only on lab tests. Lab scores are useful for debugging, but it is field data that decides your status in Search Console, and the two often disagree.

Rendering and JavaScript SEO

If your content is assembled in the browser, the crawler can end up indexing an empty shell. We check what Googlebot actually receives, then fix it at the framework level: server rendering or static generation in Next.js and React, hydration that does not block interaction, and correct indexing of anything that used to exist only after the JavaScript ran.

How we work, step by step

  1. Prioritised technical audit: a full crawl of the site plus analysis of Search Console and field data. Every issue gets a rating for impact on visibility and cost to fix, so the work starts with what pays the most.
  2. Implementation plan: a concrete task list with instructions for the developer and an estimate in hours. No tickets that say "improve speed".
  3. Implementation: our developers make the changes, or your team does under our supervision.
  4. Verification: fixes validated in Search Console, Core Web Vitals measured again, a before-and-after report.
  5. Monitoring: recurring crawls and alerts, so that the next platform update does not quietly undo the work.

What you actually receive

Most agencies sell the audit and stop there: sixty pages of PDF that nobody knows how to implement. For us the audit is the starting point, not the product.

Platforms we optimise

WordPress and WooCommerce

Our most frequent job. Plugins, caching, images and the database, plus matching the hosting to the real size of the store.

Shopify

Theme, third-party apps and tracking scripts, which are usually what kills INP on a Shopify store.

PrestaShop

Crawl budget and duplication caused by filters and product variants, plus performance on large catalogues.

Next.js and React

Rendering strategy (SSR, SSG), hydration, JavaScript SEO and correct indexing of client-rendered content.

Custom builds

We work directly with your development team at the level of code, server configuration and CDN.

What it costs

We publish ranges, which most agencies do not. We invoice in Polish zloty and these are Polish market rates, so it is worth comparing them against your local quotes.

What moves the number: how many pages you have, what the site is built on, whether developers are available on your side, and how deep the Core Web Vitals work has to go.

How you will know it worked

We report against measurable KPIs, always measured before and after: the mobile PageSpeed score, Core Web Vitals status in Search Console (how many URLs are rated good), the number of indexed pages and how fast new ones get in, and organic visibility tracked in Ahrefs.

One implementation, as an example of the scale: a WooCommerce store with a few thousand pages. After image compression, the removal of render-blocking resources and deferred scripts, LCP and INP moved into the range Search Console rates as good, and the duplicate filter URLs that had been eating the crawl budget dropped out of the indexing queue. We do not publish specific before-and-after values without stating the tool, the period and the scope of measurement; for your own site you get them in the before-and-after report.

A side effect worth naming: a fast, well-structured site with clean schema markup is also better raw material for AI search. How that connects to being quoted by ChatGPT and Perplexity is on the GEO page and in the article on the difference between SEO, AEO and GEO. More proof is in the case studies.

Tools we use

Screaming Frog for full crawls and log analysis, Google Search Console for indexing and Core Web Vitals status, PageSpeed Insights and Lighthouse for performance diagnostics and field data, Ahrefs for visibility and monitoring. Tool costs are included in the price of the service.

Frequently asked questions

What does technical SEO cover?

Crawling and crawl budget, the XML sitemap and robots.txt, URL structure, redirects and 404 errors, duplicate content, structured data, the mobile version, HTTPS and page loading speed.

What are Core Web Vitals and what counts as a good score?

They are the metrics Google uses to measure real user experience. Google treats LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1 as good. INP replaced the older FID metric.

Does page speed affect Google rankings?

Yes. Core Web Vitals are a ranking factor, and a slow site also hurts conversion and indexing, so speed work pays off in search results and in sales at the same time.

How long does technical SEO work take?

The audit usually takes 1 to 2 weeks and the implementation 2 to 8 weeks depending on scope. The effect normally becomes visible in Search Console 4 to 12 weeks after the fixes go live.

How is a technical SEO audit different from a full SEO audit?

A technical audit looks only at the technology of the site: crawling, indexing, performance and code. A full audit adds content, the link profile and competitor analysis.

How much does technical SEO cost?

A technical audit starts at around 1,500 PLN for a smaller site. A basic audit runs from about 500 to 1,500 PLN, a small or mid-size site typically 1,200 to 4,000 PLN, and large stores and portals 8,000 to 30,000 PLN. Implementation is usually billed by the hour at about 100 to 300 PLN, depending on the technology and the number of pages.

How do I check whether my site has technical problems?

Free tools give the first signal: PageSpeed Insights, the Core Web Vitals report and the indexing report in Google Search Console. A full crawler audit, for example with Screaming Frog, gives the complete picture.

More answers about working with us are in the FAQ.

Where to go next

Send us a URL. We will tell you what is broken.

A free first pass on indexing, Core Web Vitals and the usual visibility blockers. You get a quote for the audit and the implementation within 24 hours, with no obligation. This is the quick technical check, not the full free SEO and GEO audit, which takes five working days.