First, make already-prepared fixes reach the real website. Then improve the homepage and service links. Finally, check what Google and real customers do. Each step below says where you will see the result.
PLAN FOR REVIEW · CLIENT SITE NOT CHANGED
First, the plain-English picture
Csupi has a static website. There is no WordPress backend. Website changes are edits to HTML/redirect files, copied into dist, then published through Cloudflare Pages. Search Console is Google's report card, not the website editor.
Public website
Visitors see new wording, buttons, and working links as soon as a verified release is live.
Google Search Console
Google reports crawls, indexing, impressions and clicks later. Those numbers do not change instantly when we publish.
Business outcomes
A search click or phone-button tap is not a connected call or a job. Those require a separate real-world record.
The evidence we are acting on
Prepared fixes are not fully live
The 17 September remediation was saved locally, not deployed. The 29 September live read still found the old plural sitemap URL returning 404. This needs a careful release.
The working sitemap is already healthy
Search Console showed /sitemap.xml as Successful on 17 September. The old /sitemaps.xml is a separate failed historical submission. Its failure is not a sitewide penalty.
The homepage gets local search exposure
A fresh Search Console read for 30 August–26 September (28 dates) showed the homepage for “autómentés budapest”: 101 impressions, 0 clicks; “autómentés pest megye”: 114 impressions, 1 click. The earlier OpenSEO sample spans 29 inclusive dates; keep the exact 28-day cohort for comparison.
Two visible page issues
The current homepage source says “Autómentés” and has “azonal” in the hero. Its van and machinery service cards have no direct link, although links appear lower on the page. Confirm live/source parity before editing.
Search Console's 66 historical 404 rows are mostly old migration URLs, not 66 broken current pages. The two current URLs that were unknown to Google on 17 September need a fresh URL Inspection check.
The work, in the order I would do it
1 · ReleaseShip the prepared cleanups safely.
2 · ClarifyMake the towing homepage more specific.
3 · ConnectMake service cards lead to their pages.
4 · MeasureCompare Google signals and real enquiries.
Budapest/Pest towing is the first reversible page focus because the homepage already receives those queries. Search data cannot tell us whether van or machinery jobs are more profitable. If your business priority is different, this focus can change before execution.
1
Confirmed release gap · first
Put the September fixes on the real site
A useful patch already exists, but the public site still shows signs of the older version. The job is to reconcile it with today's live site and ship only the intended fixes.
On the website
Unverified minute-by-minute arrival promises disappear; callers see wording that asks them to confirm timing by phone. Relevant old URLs land on the matching current page. Dead old pages stay real 404s. /sitemap.xml remains available.
In Search Console
The current sitemap should remain Success. Old 404 totals and the failed plural submission can remain in the report until Google recrawls or the old submission is separately removed. They are not the launch score.
In site files / Cloudflare
Compare September's root HTML, redirect map, sitemap and dist with the dirty checkout and live payload. Preserve GTM, consent and phone actions. Deploy the exact reconciled patch to Cloudflare Pages production with a rollback.
Done when: production receipt plus live HTML/HTTP checks show the expected copy, sitemap, relevant redirects and intentional 404s; phone/consent/tracking and desktop/phone layouts still work.
SEO basis: Google recommends relevant permanent redirects and warns against irrelevant homepage redirects; sitemaps aid discovery without guaranteeing indexing. Redirect guidance · Sitemap guidance.
2
Small content test · after release
Make the homepage say where Csupi helps
The prominent heading is generic, though the site already appears for Budapest and Pest searches. The HTML title already says Budapest, so this is a visible page-clarity test, not a keyword-stuffing exercise.
Current visible headline
Autómentés
Proposed visible headline
Autómentés Budapesten és Pest megyében
Also fix “azonal” → “azonnal” and add one short, owner-checked sentence explaining service area and what the caller should have ready. Keep the call button prominent. Proposed wording is not published copy yet.
On the website
The headline and supporting line change immediately after publication, including on a phone screen.
In Search Console
Performance → Search results: save the exact query-and-homepage baseline, then compare clicks, impressions, CTR and position after four to eight weeks. Google may choose a different visible title or snippet.
In site files / Cloudflare
Edit only homepage source and dist. Keep the existing local title unless a real search-result check finds it inaccurate or unhelpful.
Done when: the new heading and corrected sentence are visible on the public desktop and phone page, with an exact pre-change 28-calendar-day query/page baseline saved. A ranking lift is not a release condition.
SEO basis: Google recommends clear, descriptive page titles and useful page content, and may use prominent headings to form title links. Title-link guidance · People-first content.
3
Small usability + discovery fix
Make the van and machinery cards clickable
The visible service cards describe these jobs but do not offer a direct link there. Visitors have to find separate links lower down.
Two obvious, tappable links appear in the existing cards. No new page or URL is created.
In Search Console
There is no instant “links fixed” metric. URL Inspection and later crawling can show whether Google knows the service pages; visitor clicks can be checked separately.
In site files / Cloudflare
Add ordinary HTML links to the existing target URLs in homepage source and dist. Keep navigation and phone links intact.
Done when: both links reach the right live pages and work on a phone and with JavaScript disabled.
SEO basis: Google recommends crawlable links with concise, descriptive anchor text to help people and Google understand destination pages. Link guidance.
4
Measurement · no instant result promised
Check whether Google and customers respond
A click is not a completed tow. This step keeps Google's search signals and actual enquiries separate.
On the website
No extra widget or tracking pop-up is needed. The visitor should still see the same working phone action.
In Search Console
Preserve the 30 August–26 September 28-day query/page baseline. Inspect the two current URLs that were unknown on 17 September. Recheck the same search cohort after four to eight weeks; do not demand an immediate indexed-count jump.
In operations
Record qualified calls/jobs from a real source if one exists. If it does not, mark the outcome unavailable; phone-button events stay a separate intent proxy. No Google Ads, GTM or GA4 setting change is included.
Done when: the dated Search Console comparison and a clearly labelled real-outcome or unavailable line are in the handoff, without attributing a job to SEO from a click alone.
SEO basis: Google's Performance report defines clicks, impressions, CTR and position; URL Inspection shows Google's last indexed view and may lag the live page. Performance report · URL Inspection.
What did the SEO-tactics “hacks” check add?
The existing August SEO Slides run assessed all 62 tactics in its registry; the package passed exact-one coverage validation. I used that dated assessment to filter ideas, then checked current Google guidance. It is not a fresh audit of today's site.
Use now: clear links and honest copy
Both have a concrete place on the current homepage. The links are missing from the cards; the headline and typo are visible. These are ordinary Google-supported practices.
Use later: real proof
One genuine, owner-confirmed job example with an owned photo could strengthen a service page. Existing site photos mean this is an addition only if it adds information customers need.
Maps: verify before repeating work
The business listing was improved in August. Check its current facts and reviews first; request genuine reviews after completed jobs without incentives or filtering customers by sentiment.
Skip the shortcuts: no mass city-swap pages, paid ranking links, fake clicks, incentivized reviews or self-serving star markup. They either risk Google's policies or have no reliable value for this client. Google spam policies · Review rules · Review-rich-result limits.
Why the Google Business Profile is not in the first release
Google local results consider relevance, distance and prominence. A profile edit cannot fix the user's physical distance, and prior profile work may already cover the obvious fields. Only a fresh read of the exact profile can justify a change. If a genuine gap exists, the update will appear in Maps/Search, not the website files. Google local-ranking guidance.
How you will know this plan was carried out
Immediately after release: open the bare public website and test the exact wording, links, redirects, phone action and mobile layout. Keep the Cloudflare deployment receipt and rollback.
After Google processes changes: inspect the selected URLs and compare the same Search Console queries/pages over a like-for-like four-to-eight-week window. A sitemap or title edit is not proof of ranking.
For business impact: report confirmed qualified calls/jobs separately from clicks and phone-button taps, or mark them unavailable.
Current stage: this is a reviewable plan. The client website, Search Console configuration and Business Profile have not been changed in this round. Under the existing LLL workflow, a later explicit Launch starts execution. The public website stays reachable without a new login, token, VPN or IP gate, and Google Ads remains read-only.
If Matt does not name a preferred service, the first reversible test stays on Budapest/Pest towing. A different service priority can be chosen before Launch without rebuilding the technical release.