Buy the auditfrom CZK 14,900
+420 602 575 587support@seoflower.com
Buy the audit

Your cart

0 items

Foundations · Sprint or monthly

Fix what search engines can't get past.

Wrong canonicals, blocked resources, slow templates, broken redirects. We find them, ticket them and check each one is fixed.

  • Pages not indexed
  • Traffic dropped after a move
  • Slow on mobile
  • Duplicate URLs

from CZK 19,900 / mo

See what's included

You might notice

What you might notice

  • Pages you published months ago still don't appear in Google.
  • Traffic fell after a migration and never came back.
  • Search Console shows thousands of "Crawled, not indexed" URLs.
  • The site feels slow on a phone, and developers say it's fine.
  • The same product is reachable on five different addresses.
  • A new release quietly broke redirects or canonical tags.

Specimen

A crawl graph, annotated

HOMESofasTablesLamps301 · 301 · 301NO INLINKSDUPLICATES
Specimen: crawl graph with broken paths highlighted, modelled.
  1. A: Pages search engines reach in few clicks.
  2. B: A chain of redirects that wastes crawl effort.
  3. C: Orphan pages with no internal links.
  4. D: A cluster of near-duplicate URLs.

Every fix is a ticket

  • Full crawl and index analysis
  • Ticket for every fix: what, why, how we verify
  • Core Web Vitals and template speed review
  • Redirect map and migration clean-up
  • Structured data check
  • Before-and-after verification crawls
  • Weekly check-in during the sprint (sprint) · Monthly report on the 5th (care)

Sample ticket · modelled

What to change
Add a self-referencing canonical to all product template pages.
Why
Without it, search engines choose their own version of each page.
How we verify
Re-crawl the template and confirm 100% of sampled URLs return the canonical.
Effort / impact
Low / High

Prices and options

Foundations · Sprint or monthly

Choose an option

CZK 34,900

one-off · excl. 21% VAT · no contract

Delivery

Digital. Your start date is confirmed by email. Turnaround is shown on each option.

Terms and refunds

One-off projects: full refund before kick-off. Monthly services: three-month minimum, then 30 days' notice. Consumers have 14 days to withdraw.

Read the refund policy

What you get

Everything in the list above, delivered in plain language. See what's included.

Support

Questions before you buy? support@seoflower.com or +420 602 575 587.

Not sure? See the estimatorAsk about a custom scope

Fix sprint

CZK 34,900

A prioritised backlog, worked over six weeks · 6 weeks

  • Backlog built from your audit or a fresh crawl
  • Tickets for each fix
  • Weekly 30-minute check-in
  • Verification crawl before and after
  • Closing summary of what changed

One-off. excl. VAT.

Ongoing technical care

CZK 19,900 / month

Monthly monitoring and ticketing · Monthly, reports on the 5th

  • Monthly crawl and index monitoring
  • New issues ticketed
  • Check after each release you tell us about
  • Core Web Vitals tracking
  • Monthly report

Billed monthly in advance. 3-month minimum, then 30 days' notice. excl. VAT.

What drives the cost

  • Site size and crawl complexity
  • Number of page templates
  • Platform and how easy it is to change
  • How much developer time you have
  • Whether there is a migration in progress

Use the cost estimator

Also included in Seed (Technical care), Bloom (Technical care), Flourish (Technical care).

How the six-week sprint runs

See the full process

  1. Week 1

    Baseline

    Crawl, index check and a ranked backlog.

  2. Weeks 2 and 3

    First fixes

    Highest-impact tickets handed to your developers.

  3. Weeks 4 and 5

    Next wave

    Second batch, plus checks on what shipped.

  4. Week 6

    Verify

    Re-crawl, compare to baseline, close the sprint.

Technical SEO questions

More questions

Do you make the code changes?

Usually no. We write and verify the tickets, and your developers implement them. For simple CMS changes we can do it ourselves if you give us access.

Sprint or care, which one?

Choose the sprint if the site has a pile of known problems. Choose care if the site is healthy and you ship changes often.

Do I need an audit first?

Not if you have a recent one. If you don't, the sprint starts with a crawl that works as a lightweight audit.

What happens at the end of the sprint?

You get a summary of what shipped and what is left. You can move to care or stop. There is no obligation.

Illustrative example

An illustrative example

A modelled scenario: a shop repairs redirects and duplicate URLs after a platform move.

Modelled scenario showing how we work. Not a named client result.

Read the case: E-shop category recovery

ILLUSTRATIVE TREND

Fewer errors, more indexed pages.

Six weeks to a cleaner site, or a monthly watch on it.

Ask a question