Technical SEO: what the search engine needs to understand your site.

Crawling, indexing, structured data and architecture. What the search engine needs to read your site: sitemaps, canonicals, schema and redirects.

Let's fix what Google cannot read

Diagnosis from €50 · WordPress · PHP · WooCommerce · Gravity Forms · Elementor · Plugins · Timeline defined after diagnosis

Page contents
  1. 01 What technical SEO is and what it is not
  2. 02 What it covers and what it does not
  3. 03 How we do it
  4. 04 Price and scope
  5. 05 Timelines and response
  6. 06 Compatibility and access
  7. 07 What evidence we deliver
  8. 08 What you receive
  9. 09 What happens next
  10. 10 Frequently asked questions
  11. 11 If this is not what you need
  12. 12 Let's fix what Google cannot read

01What technical SEO is and what it is not

Technical SEO is not writing titles with keywords. It is making sure Google can crawl, understand and index what already exists: URLs, canonicals, sitemap, robots, schema, redirects and Core Web Vitals.

We work on the real site, with Search Console and our own crawling. No ranking or traffic is promised: what blocks reading is fixed, before and after is measured, and it is documented.

The promise is concrete: verifiable diagnosis, explained changes and evidence of crawling and indexing. Whatever depends on content, authority or the algorithm is stated and kept separate.

We do not sell rankings

Technical SEO removes obstacles; it does not guarantee rankings. If someone promises the number one position, it is not this service.

02What it covers and what it does not

Includes

  • Crawling and indexing: robots, sitemap, canonicals, noindex and redirects.
  • JSON-LD schema and structured data, without duplicating the SEO plugin.
  • Migrations: URL inventory, redirects and signal preservation.
  • Core Web Vitals as a technical factor, with before/after measurement.
  • Review of metadata and internal linking architecture.
  • Report with findings, priority and evidence.

Does not include

  • Copy, keywords, content or link building.
  • Guarantee of rankings, traffic or conversion.
  • Design, development or platform migration.
  • Licenses for plugins, SEO tools or third-party services.
  • Campaigns, media or social media management.
  • Ongoing maintenance.

03How we do it

  1. 01

    Measure

    Crawling, Search Console, sitemap and CWV; the real state is documented before touching anything.

    What is needed URL, Search Console access, WordPress and a person who validates.

  2. 02

    Prioritize

    What blocks indexing is separated from what merely improves; prioritization is by impact and risk.

    What is needed Validated priorities and access.

  3. 03

    Fix

    Robots, canonicals, sitemap, schema, redirects and metadata, with staging and rollback.

    What is needed Working window and scope confirmation.

  4. 04

    Verify

    Crawling and indexing are run again and compared; regressions are checked.

    What is needed Search Console access and validation.

  5. 05

    Report

    Delivered: what was fixed, what was not and what depends on content or authority.

    What is needed Someone who validates the result.

04Price and scope

Technical diagnosis from €50. Implementation is quoted afterwards, with the scope closed: which URLs, which page types and which changes. No payment is taken for a promise of rankings.

What determines the costNumber of URLs and templates: a 20-page site does not cost the same as a catalog. · Migration and redirects: inventory, mapping and verification that nothing breaks. · Schema and metadata: what the plugin emits, what is missing and what is duplicated. · CWV and performance: if the technical problem is loading, it is coordinated with WPO. · Search Console and verifications: access, crawling and follow-up checks. · Coordination with development or content: what is not solved from the dashboard.

  • Number of URLs and templates: a 20-page site does not cost the same as a catalog.
  • Migration and redirects: inventory, mapping and verification that nothing breaks.
  • Schema and metadata: what the plugin emits, what is missing and what is duplicated.
  • CWV and performance: if the technical problem is loading, it is coordinated with WPO.
  • Search Console and verifications: access, crawling and follow-up checks.
  • Coordination with development or content: what is not solved from the dashboard.
See starting prices

05Timelines and response

The timeline is defined after the diagnosis. No date is promised before knowing how many URLs there are and what page types exist.

The first response confirms whether the problem is technical, of content or of authority. Not everything is fixed with a plugin.

If access, Search Console or decisions are missing, the timeline starts when they are resolved. Waiting time is not discounted from the work or hidden.

There is no implicit SLA behind this page. Indexing depends on Google and cannot be controlled; whatever is committed is written in the proposal.

Response policy: First response within 1 business day, Monday to Friday, Colombia and Spain time.

06Compatibility and access

We work on WordPress, Rank Math, PHP, MySQL, Search Console, sitemap, robots, JSON-LD schema and CWV. The installed stack is part of the diagnosis.

To start we need: URL, WordPress access, Search Console, hosting/SFTP if there are file changes, sitemap and a person who validates.

Before touching anything: backup, staging and a rollback plan. Robots, canonical or redirect changes are tested before publishing.

The plugin schema is not duplicated: it is decided what each layer emits and it is documented. Rank Math covers metadata, canonicals, sitemap and redirects; custom schema covers what the plugin must not duplicate.

07What evidence we deliver

We do not publish client metrics without permission. There are no invented ranking, traffic or "number one spot" figures: the evidence is the crawl, the indexing and the report.

  • Crawl: URLs found, URLs blocked and errors.
  • Indexing: what gets in, what stays out and why.
  • Schema: what is emitted and what is removed to avoid duplication.
  • CWV: before/after measurement, if it is in scope.

If there are publishable cases with permission, they will appear with source and date; until then, nothing is invented.

08What you receive

Deliverables and delivery timing
Deliverable When
Technical diagnosis and priorities Before touching
URL and redirect inventory Before migrating or changing
Applied and verified changes At implementation close
Crawling and indexing evidence Along with the report
Open items and dependencies At closing

09What happens next

Technical SEO does not end with the report: an update, a migration or a template change can break what was already working.

Optional maintenance starts at €50/month and includes updates, backups, security review and an alert when something fails. The follow-up SEO review is quoted separately.

It is not mandatory. The report leaves priorities and checks so your team or agency can maintain them.

See support and maintenance

See support and maintenance

10Frequently asked questions

Do you guarantee the number one position?

No. The technical part is fixed and documented; rankings depend on content, authority and the algorithm. Promising a ranking is not this service.

What does technical SEO include?

Crawling, indexing, canonicals, sitemap, robots, schema, redirects and CWV within the scope. Content, keywords and link building are quoted separately.

Is it the same as content SEO?

No. Technical SEO removes obstacles so Google can read and index; content and authority are another layer, with another scope and another budget.

How much does it cost?

Technical diagnosis from €50; implementation is quote-based after reviewing URLs, page types, schema and the needed changes.

How long does it take?

It is defined after the diagnosis. Indexing depends on Google and no date is promised; whatever is committed is written in the proposal.

Do you work with Rank Math?

Yes. It is documented what the plugin emits and what the custom schema emits, so canonicals, metadata and structured data are not duplicated.

Next step

12Let's fix what Google cannot read

Send us the URL and Search Console access. We will tell you what can be crawled, what is blocked and what can be fixed without promising rankings.