From a2ca6eb4130b53d08b81f9dda3742b620506b798 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Wed, 14 Oct 2026 18:51:30 +0200 Subject: [PATCH] =?UTF-8?q?Website:=20a=20page=20for=20people=20who=20sear?= =?UTF-8?q?ch=20=E2=80=9Efelh=C5=91=20t=C3=A1rhely"=20(R-1033..R-1035)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Search Console (3 months, read 2026-10-14): 48 impressions, 1 click, average position 73.6; the top query is „felhő tárhely" (19). No page on the site used the phrase — Google was showing the home page by accident. New pair /sajat-felho-tarhely + /en/own-cloud-storage: what cloud storage is and the three ways to have one; what to do when the Google or iCloud storage is full (the free clean-up first, linked to Google's and Apple's own help; the paid options second); a five-year cost table; where the data sits; who should NOT choose this; the closed test. Registered in site_gates.py TWINS/URL/SHELL, both URLs in sitemap.xml (22 -> 24). FAQPage JSON-LD derived from the visible text. Prices each read 2026-10-14 on the provider's own Hungarian page, with the URLs and the date in an HTML comment and a visible „Árak" line: Google AI Plus (2 TB) — Google One's 2 TB plan — 35 990 Ft/év (behind the „Éves" toggle; a plain fetch sees only the monthly 3 590 Ft), iCloud+ 2 TB 4 490 Ft/hó, Microsoft 365 Családi (2 TB shared, no longer 1 TB per person) 46 499 Ft/év. Felhom's own cost follows what the site already said (operator ruling): machine and install one-off, power, off-site storage monthly by volume, operation OPTIONAL, no fee during the closed test. Power is stated as an idle measurement (nyugalmi állapotban 7-9 W, ~75 kWh/év, from audits/night-power-2026-10-13) and the page says a year with daytime use is more; no daytime figure and no electricity tariff are given, because neither is measured or sourced. FAQ corrected (both languages, JSON-LD re-derived): the cost answer carried unsourced, undated prices and summed Spotify and a password manager into a storage comparison; and the page contradicted itself on electricity („havi néhány ezer forint" vs „évi 5.000–15.000 Ft"). App count 60 -> 62 in the four places that were stale. Three defects found on the rendered page and fixed: a .vs-row link fell back to the browser-default blue (contrast 1.99 -> 7.17); 24px of horizontal scroll at 390px because .method-pros li is a nowrap flex row and the new items contain links (each item's content wrapped in one span); .info-card and .method-pros were scoped to the pages that first used them. site.css ?v=31 on all 26 pages. The shared .content-section padding was NOT changed — it is identical on every page; the new page only lacked the alt-bg alternation, and now has it. R-1033 the apps page lags the catalog by two apps (plant-it, wger); R-1034 gate 17 checks the FAQ JSON-LD on two hard-coded pages only; R-1035 the SEO result, with dated checks on 2026-11-11 and 2026-12-09. --- REPORT-seo-felho-tarhely-2026-10-14.md | 194 ++++++++++++ STATUS.md | 6 +- .../audits/seo-2026-10-14/BASELINE.md | 90 ++++++ documentation/backlog/OPEN-ITEMS.md | 11 +- scripts/site_gates.py | 5 + website/404.html | 2 +- website/CHANGELOG.md | 51 +++- website/adatkezeles.html | 2 +- website/alkalmazasok.html | 2 +- website/assets/site.css | 49 +-- website/biztonsagimentes.html | 3 +- website/en/apps.html | 2 +- website/en/backups.html | 3 +- website/en/contact.html | 2 +- website/en/download.html | 2 +- website/en/faq.html | 20 +- website/en/index.html | 4 +- website/en/own-cloud-storage.html | 289 ++++++++++++++++++ website/en/services.html | 4 +- website/en/sizing.html | 2 +- website/en/technology.html | 2 +- website/en/testing.html | 2 +- website/feltetelek.html | 2 +- website/gepigeny.html | 2 +- website/gyik.html | 20 +- website/index.html | 8 +- website/kapcsolat.html | 2 +- website/letoltes.html | 2 +- website/sajat-felho-tarhely.html | 289 ++++++++++++++++++ website/sitemap.xml | 16 + website/szolgaltatasok-nonpublic.html | 2 +- website/szolgaltatasok.html | 6 +- website/technologiak.html | 2 +- website/teszteles.html | 2 +- 34 files changed, 1023 insertions(+), 77 deletions(-) create mode 100644 REPORT-seo-felho-tarhely-2026-10-14.md create mode 100644 documentation/audits/seo-2026-10-14/BASELINE.md create mode 100644 website/en/own-cloud-storage.html create mode 100644 website/sajat-felho-tarhely.html diff --git a/REPORT-seo-felho-tarhely-2026-10-14.md b/REPORT-seo-felho-tarhely-2026-10-14.md new file mode 100644 index 00000000..8f1fcbf4 --- /dev/null +++ b/REPORT-seo-felho-tarhely-2026-10-14.md @@ -0,0 +1,194 @@ +# REPORT — the „felhő tárhely" page, 2026-10-14 + +*Written as `REPORT-.md` because two other sessions shipped in this repo today and the shared +`REPORT.md` is overwritten (repo `CLAUDE.md`).* + +--- + +## For the operator, in plain words + +Google showed felhom.eu 48 times in three months and got 1 click, at average position 73.6 — page 8. +The commonest search was „felhő tárhely", and **no page on the site used those words**, so Google was +showing the home page by accident. + +There is now a page that does: **felhom.eu/sajat-felho-tarhely**, with an English twin. It explains +what cloud storage is, what to do when a Google or iCloud account fills up (**the free clean-up +first** — that is what most people actually need — and the paid options second), what five years +costs with today's prices, where the data sits, and **who should not buy this**. + +**You asked me three questions and I followed all three answers.** The page shows Felhom's cost the +way the site already described it, so nothing new is promised. The English twin was written, because +a gate requires one. The app count says 62, which is what the apps page really shows. + +**Two things need you:** + +1. **Ask Google to index the page**: Search Console → URL-ellenőrzés → `https://felhom.eu/sajat-felho-tarhely` + → „Indexelés kérése". Until that happens the page may sit unseen, and the two checks below will + read zero for a reason that has nothing to do with the page. +2. **Two dates are in the register**: 11 November and 9 December. On each, you read three numbers out + of Search Console and I record them. **A nothing-happened result on 11 November is normal** — a new + page on a site at position 73.6 takes weeks to months to move. That is why there are two dates. + +**Be patient with this one.** „felhő tárhely" on its own is held by Microsoft, Google and the big +comparison sites, and we will not take it soon. The page aims at the longer searches Google itself +suggests next to it. This is a slow channel and it does not replace talking to people. + +**What I corrected while I was in there:** the FAQ's cost answer quoted prices with no source and no +date, and added Spotify and a password manager into a storage comparison. It now carries the three +real storage prices with the day I read them. The same page also contradicted itself about +electricity — one answer said a few thousand forints a month, another said 5–15 thousand a year. Both +now say the measured figure. + +--- + +## 1. The STOP 1 answers, and what they changed + +| question | your answer | what I did | +|---|---|---| +| How does the page show Felhom's cost? | Reuse what the site already says | Machine one-off, install one-off, power (measured), off-site storage monthly by volume, **operation optional**, no fee during the closed test. The reviewer's own option (a) would have read as a **mandatory** monthly fee and contradicted `index.html` („ha kéred, az üzemeltetést") and the FAQ („opcionális"). | +| The English twin | Build it in the same commit | `/en/own-cloud-storage`, registered as a `TWINS` pair. | +| The app count | 62 everywhere, file the lag | Four „60" spots corrected; `plant-it` and `wger` filed as **R-1033**. | + +### The „what do I keep if I stop paying?" check you asked for + +**A value is ruled; a procedure is not.** + +- `architecture/01-topology-and-trust.md` §10 — **„Never hold data hostage"**: subscriptions cover + ongoing labour, and the customer's data and deployed apps stay recoverable by the customer via the + recovery code, with nothing locked behind the operator. +- The same file, §11 — **„Offboarding / decommission (scenario 6) — not yet designed."** + +So the page repeats only what `index.html` already says („A gép a tiéd", the recovery code opens the +off-site copy) and **describes no exit procedure**, because none exists to describe. + +## 2. What is live + +| | | +|---|---| +| Hungarian | `https://felhom.eu/sajat-felho-tarhely` | +| English twin | `https://felhom.eu/en/own-cloud-storage` | +| Title (59 chars) | Saját felhő tárhely otthon – Google One helyett \| Felhom.eu | +| Description | Mi az a felhő tárhely, mit tegyél, ha megtelt a Google vagy az iCloud tárhelyed, és mennyibe kerül öt év alatt a saját gép. Mai árakkal és mért fogyasztással. | +| Structured data | FAQPage, 4 questions, **derived from the visible text** so the two cannot disagree | + +### The price table, and where each number came from + +All read **2026-10-14**, each on the provider's own Hungarian page. + +| plan | price | 5 years | source | +|---|---|---|---| +| Google AI Plus (2 TB) — Google One's 2 TB plan | 35 990 Ft/év | 179 950 Ft | `one.google.com/about/plans?hl=hu`, „Éves" toggle | +| iCloud+ 2 TB | 4 490 Ft/hó | 269 400 Ft | `support.apple.com/hu-hu/108047` | +| Microsoft 365 Családi (2 TB shared) | 46 499 Ft/év | 232 495 Ft | `microsoft.com/hu-hu/…/compare-all-microsoft-365-products` | + +**Two naming facts that will age.** Google's 2 TB tier is branded **„Google AI Plus"** on the card +while the site is Google One and Google's own copy says „Google One-csomag" — the page carries both. +**Microsoft 365 Családi is 2 TB shared**, no longer 1 TB per person. Google's yearly price is behind +a JS toggle: a plain HTTP fetch sees only the monthly 3 590 Ft, so a future re-check must use a +browser. + +**No electricity tariff is quoted anywhere.** I could not source a 2026 Hungarian residential Ft/kWh +rate I would stand behind, so the page gives kWh and „néhány ezer forint" and lets the reader do the +arithmetic. Inventing a tariff would have been a fabricated number on a public page. + +**Power is stated as an idle measurement**, from `audits/night-power-2026-10-13/` (N100: 7.3 W +median, 8.5 W average, 66 Wh over a normal night → ~75 kWh/year): „nyugalmi állapotban 7-9 W … +nappali használattal ettől több." **No daytime figure is given — there is no measurement for one.** + +## 3. The FAQ change, before → after + +| | before | after | +|---|---|---| +| „Megéri anyagilag…" | „Google One 2TB évi ~36.000 Ft, iCloud 2TB évi ~45.000 Ft, Spotify család évi ~30.000 Ft, jelszókezelő évi ~15.000 Ft … évi 120.000+ Ft" — no source, no date, and non-storage services summed into a storage comparison | the three storage prices above with the date read, the five-year totals, the Felhom side per STOP 1, and „ha 200 GB alatt elférsz, a felhőszolgáltató marad az olcsóbb" | +| „Vannak rejtett költségek?" | „villanyáram (**havi** néhány ezer forint)" | „villanyáram (nyugalmi állapotban mérve évente nagyjából 75 kWh, néhány ezer forint)" | +| „Mennyi áramot fogyaszt…" | „15-35 watt … évi 5.000–15.000 Ft", unsourced | the measured N100 and HP t740 figures, with the idle caveat | + +The first two answers **contradicted each other** on the same page (a few thousand a month vs 5–15 +thousand a year). Both English twins moved with them; the FAQ JSON-LD was re-derived so gate 17 still +sees it equal to the visible text (42 question/answer pairs on each FAQ page). + +## 4. Three defects found by looking at the rendered page + +None of these would have been caught by reading the HTML. + +1. **A link at contrast 1.99.** The `/gepigeny` link inside a `.vs-row` cell rendered in the + **browser-default blue** `rgb(0,0,238)` on the near-black background. The site's link rule covers + `.content-section p a` and `li a` but not a bare `div`. `.vs-row a` added → **7.17**, the site's + own link colour. This also protects the home page's comparison block. +2. **24 px of horizontal scroll at 390 px.** `.method-pros li` is `display:flex; flex-wrap:nowrap`; + the existing pages' items are plain text (one flex item), mine contain links and ``, so + each became a separate flex item on a nowrap row. Each item's content is now one ``. + **My first fix was wrong and the screen caught it:** `overflow-wrap:anywhere` made the overflow + number go away while splitting words into vertical columns. Reverted. +3. **The new page rendered unstyled.** `.info-card` was scoped to `.page-technologiak`/`.page-teszteles` + and `.method-pros` to `.page-biztonsagimentes`. Both scopes now name the new page, the same way + `.vs` does. + +**The section-gap question you raised:** `.content-section { padding: 80px 0 }` (60 under 600 px) is +**identical on this page, `biztonsagimentes` and `technologiak`** — measured at 1440 px and 390 px. +The gap was never this page's own. What the other pages have and this one lacked is the `alt-bg` +alternation (`biztonsagimentes` runs `. A . A`), which turns 160 px of space into a band boundary. +The page now runs `. A . A . A`. **The shared padding was not touched**, on your instruction. + +## 5. Verification + +- `site_gates.py` **green**: BOM, zero emoji, sidebar/footer identical per language set, analytics, no + CDN, design tokens, no `