Growth Audit — August 3, 2026
US Users · roomsketcher.com

RoomSketcher Growth Audit: The Outside View

Search visibility, AI discovery, paid efficiency, an external read on what's working, what isn't, and what to act on this cycle. Scoped to US users on roomsketcher.com.

Prepared for RoomSketcher August 3, 2026 Prepared by Kworq
Report Period: July 20 – August 2, 2026  ·  Issue #8  ·  Next Report: August 17, 2026

Growth Scorecard (US)

Every figure below is filtered to United States users on roomsketcher.com. Session and click metrics are reported as daily averages so windows of different length stay comparable. The Δ column compares Current against Baseline (the immediately prior 14 days); the Last Reported column is what Issue #7 showed, included here only because five weeks passed between calls.

KPILast Reported
Jun 15 – Jun 28
Baseline
Jul 6 – Jul 19
Current
Jul 20 – Aug 2
Δ vs BaselineStatus
Website Traffic (US) — daily averages
Total Website Sessions4,218/day4,459/day4,350/day-2.4%
Direct Sessions2,121/day2,243/day2,231/day-0.5%
Organic Search Sessions1,212/day1,309/day1,102/day-15.8%
Paid Search Sessions (Google)328/day348/day460/day+32.0%
Paid Other Sessions (Microsoft)228/day267/day232/day-12.9%
Referral Sessions69/day78/day74/day-4.0%
Email Sessions39/day41/day38/day-6.7%
Organic Social Sessions29/day37/day33/day-10.4%
Website Sessions by Channel — 21-Week TrendDaily-avg sessions/week · US · GA4 weeks start Sunday · % = change 3/8→7/260.006001,2001,8002,4003,0003/83/224/54/195/35/175/316/146/287/127/26Direct▲ 10%Organic▼ 33%Paid Search▲ 19%Paid Other▲ 0%
Bing & Alt-Engine Organic (US) — daily averages
Bing Organic Sessions73.1/day84.1/day77.9/day-7.5%
DuckDuckGo Sessions79.6/day92.1/day82.9/day-10.0%
Yahoo Sessions26.3/day27.5/day27.3/day-0.8%
AI Referral Traffic (US) — daily averages
Total AI Referral Sessions34.4/day29.7/day25.2/day-15.1%
ChatGPT28.9/day23.1/day19.7/day-14.8%
Gemini2.1/day2.2/day2.0/day-9.7%
Perplexity2.1/day3.1/day2.1/day-34.1%
Copilot0.8/day0.9/day0.6/day-25.0%
Claude0.6/day0.4/day0.8/day+120.0%
AI Referral Sessions — 21-Week TrendDaily-avg sessions/week · US · % = change 3/8→7/260.0016324864803/83/224/54/195/35/175/316/146/287/127/26Total▼ 50%ChatGPT▼ 38%Others▼ 74%
Search Console (US)
Clicks
Current window has 13 days of GSC data (normal lag)
1,146/day1,198/day1,001/day-16.5%
Impressions107,516/day100,934/day94,857/day-6.0%
Non-Brand Clicks
branded queries excluded
1,109/day918/day-17.2%
Non-Brand CTR1.103%0.972%-0.13pp
Average CTR1.066%1.187%1.055%-0.13pp
Average Position10.029.9110.26+3.5%
Search Console — ImpressionsDaily-avg impressions/week · US · % = change 3/8→7/260.0040,00080,000120,000160,000200,0003/83/224/54/195/35/175/316/146/287/127/26Impr.▼ 30%
Search Console — ClicksDaily-avg clicks/week · US · % = change 3/8→7/260.004008001,2001,6002,0003/83/224/54/195/35/175/316/146/287/127/26Clicks▼ 35%
Search Console — Avg PositionImpression-weighted rank/week · US · lower is better · % = change 3/8→7/267.78.59.31011123/83/224/54/195/35/175/316/146/287/127/26Avg pos▲ 34%
Key Head-Term Positions (US) — lower is better
“floor plan software”9.68.8-8.3%
“floorplan software”7.06.9-1.4%
“floor plan app”10.08.9-11.0%
“free floor plan software”10.15.5-45.5%
“floor plan”12.57.4-40.8%
“room planner”29.920.7-30.8%
“floor plan creator”18.721.0+12.3%
“floor plan maker”24.824.1-2.8%
Template Gallery (/floor-plan-gallery/) — scale corrected this issue
Gallery Clicks90.6/day90.6/day+0.0%
Gallery Impressions12,642/day12,223/day-3.3%
Gallery Pages Receiving Impressions833832-0.1%
Gallery Pages Receiving Clicks157166+5.7%
Google Ads — Spend & Efficiency (US, NOK converted at 0.091)
Spend1,111/day985/day1,602/day+62.6%
Clicks595/day688/day926/day+34.4%
CTR8.27%9.81%9.84%+0.03pp
Total Conversions (all actions)97.5/day125.7/day150.4/day+19.6%
Blended Cost per Conversion11.407.8410.65+35.9%
Google Ads — ROAS vs the Q3 TargetConversion value ÷ spend, per week · US · Q3 KR target = 1.0 · % = change 3/8→7/260.000.400.801.21.62.03/83/224/54/195/35/175/316/146/287/127/26ROAS▼ 34%Target▲ 0%
Google Ads — SpendDaily-avg USD/week · US · NOK at 0.091 · % = change 3/8→7/260.005001,0001,5002,0002,5003/83/224/54/195/35/175/316/146/287/127/26Spend▼ 14%
Google Ads — Free Signups (US)
Free Account (Personal)79.4/day109.1/day130.9/day+20.0%
Free Account (Business)8.6/day9.1/day10.9/day+20.5%
Google Ads — Paid Conversions (US)
New Subscription7.26/day6.11/day7.11/day+16.4%
Cost per New Subscription153161225+39.7%
Premium Project1.61/day0.89/day1.07/day+20.0%
Ready Made Purchase0.64/day0.57/day0.36/day-37.5%
Microsoft (Bing) Ads (US) — NOK converted at 0.091
Spend569/day382/day-32.9%
Clicks518/day432/day-16.5%
Total Conversions44.4/day33.2/day-25.2%
Blended Cost per Conversion12.8211.50-10.3%
New Subscription3.01/day1.64/day-45.6%
Cost per New Subscription189234+23.4%
Combined Paid (Google + Microsoft, US, USD)
Combined ROAS
conversion value ÷ spend — Q3 KR target > 1.0
0.810.60-25.9%
Google Ads ROAS (US)0.870.61-29.9%
Google Ads ROAS incl. renewals1.010.73-27.7%
Microsoft Ads ROAS (US)0.720.57-20.8%
Spend-weighted Search Impr. Share32.7%31.8%-0.9pp
Combined Spend1,555/day1,984/day+27.6%
Combined Conversions170.1/day183.6/day+7.9%
Combined Cost per Conversion9.1410.81+18.3%
Combined New Subscriptions9.12/day8.75/day-4.1%
Combined Cost per New Subscription171227+33.1%
GA4 Conversion Events (All Sources, US)
Sign-Up Rate
sign_up ÷ sessions, US
7.04%7.00%-0.6%
sign_up274.1/day314.1/day304.4/day-3.1%
begin_checkout53.7/day54.8/day55.5/day+1.3%
new_subscription17.9/day17.3/day16.6/day-4.1%
purchase33.6/day32.3/day30.9/day-4.4%
GA4 sign_up (All Sources)Daily-avg events/week · US · Q3 OBJ 2 KR input · % = change 3/8→7/260.001002003004005003/83/224/54/195/35/175/316/146/287/127/26sign_up▼ 2%
GA4 new_subscription & purchase (All Sources)Daily-avg events/week · US · % = change 3/8→7/260.0010203040503/83/224/54/195/35/175/316/146/287/127/26purchase▼ 29%new_sub▼ 30%
Site Performance (local Lighthouse — see Section 7, not PSI-comparable)
Mobile Performance (median of 4)84
Mobile LCP (median of 4)4.01s
Desktop Performance (avg of 2)94
Desktop LCP (avg of 2)1.48s
Accessibility97
SEO100
Reading the Trends
  • Paid got more expensive per unit of revenue, on both engines. Combined spend rose 28% ($1,555→$1,984/day) while combined new subscriptions fell 4% (9.12→8.75/day). Cost per new subscription went $171→$227 (+33%). Google bought 16% more subscriptions but paid 40% more each; Microsoft cut spend 33% and lost 46% of its subscriptions. Neither engine improved the metric that matters.
  • Free signups and paid subscriptions are diverging. Google Ads free accounts rose 20% while its paid subscriptions rose only 16% at a much worse cost. 94% of Google's paid conversions are free accounts — so the account is optimising toward the cheap, abundant event. This is the conversion-goal pollution flagged since Issue #1, now visibly steering budget.
  • Organic fell 16% but rankings did not. On the 200 highest-impression pages, weighted position moved just +0.09 while impressions fell 6.9% and CTR fell 6.4%. That combination is SERP-level click compression, not a demotion — and it is consistent with head-term positions actually improving this cycle.
  • All-source conversions held up better than paid did. GA4 sign_up is down only 3.1% and begin_checkout is up 1.3%, against a 16% organic session decline and a 28% paid spend increase. Demand is roughly intact; the efficiency of buying it is what changed.

The 30,000-Foot View (US)

Channel mix for the current window, July 20 – August 2, 2026. 60,898 total US sessions. Direct remains over half of all traffic — a persistent measurement question as much as a channel, addressed below.

Direct
31,232 (51.3%)
Organic Search
15,430 (25.3%)
Paid Search
6,438 (10.6%)
Paid Other (MS)
3,255 (5.3%)
Unassigned
1,172 (1.9%)
Referral
1,043 (1.7%)
Cross-network
847 (1.4%)
Email
531 (0.9%)
Organic Social
464 (0.8%)
AI Assistant
336 (0.6%)
Data period: July 20 – August 2, 2026 · US only · GA4 property 346957354 · Paid Social (91) and Organic Video (59) omitted from the chart for legibility.

The Organic Decline Is Five Months Old, Not Two Weeks Old

Reading the current window against the baseline alone understates what is happening. Weekly US organic sessions since the tracking rebuild show a steady, uninterrupted slide — and the final full week of this window is the lowest on record since measurement became trustworthy.

Wk 09 (Feb 22)
11,544
Wk 12 (Mar 15)
11,397
Wk 14 (Mar 29)
11,211
Wk 17 (Apr 19)
10,840
Wk 20 (May 10)
9,167
Wk 23 (May 31)
8,607
Wk 26 (Jun 21)
8,472
Wk 29 (Jul 12)
9,095
Wk 30 (Jul 19)
8,644
Wk 31 (Jul 26)
7,318 — lowest on record
US organic sessions per ISO week, GA4. Selected weeks shown. Week 32 excluded (partial). Tracking floor is Feb 17, 2026 — no earlier data is reliable, and therefore no year-over-year comparison is possible yet.
Critical — Diagnosed

Organic Is Down 37% — and Nine Pages Explain Over Half of It

Weekly US organic sessions have fallen from ~11,500 in March to 7,318 in the week of July 26, a 37% decline over five months with no single-week cliff. That is the symptom. The cause is narrower and more actionable than the headline suggests.

First, what kind of loss it is. Comparing March 8–April 4 against June 28–July 25: impressions fell 26.6% (133,358→97,856/day) while CTR actually improved 6.9%. Decomposed, that is −374 clicks/day from lost impressions and +72/day recovered by better click-through. The site is being shown less, not clicked less. It is not de-indexing either — 289 pages dropped out of results (0.4% of impressions) and 235 new ones replaced them, leaving the footprint stable at ~1,600 pages.

Second, where the impressions went. They are not spread evenly. Nine pages account for 55% of the entire decline, and every one of them lost rank:

PageImpr/day MarImpr/day JulΔPosition
/house-plans/3,9331,230−69%11.8 → 27.7
/kitchen-planner/3,054605−80%12.1 → 34.2
/blog/how-to-measure-floor-area/1,322265−80%2.6 → 5.1
/features/roomsketcher-app/1,666760−54%8.1 → 12.9
/features/draw-floor-plans/1,597706−56%11.4 → 20.9
/blog/how-to-read-floor-plans-9-easy-steps/79892−88%3.6 → 6.4
/download-app/637194−70%2.0 → 5.4
/subscriptions/free/549146−73%2.3 → 3.4
/home-improvement/home-remodeling-software/506179−65%14.2 → 27.0
These nine pages14,0624,177−70%55% of the decline
  • They split into two failure modes. Three pages fell off the map — /house-plans/, /kitchen-planner/ and /home-remodeling-software/ all went from page 1–2 to roughly position 28–34. A 20-position fall is structural, not drift. The other six slipped from strong positions; note that /blog/how-to-read-floor-plans-9-easy-steps/ lost 88% of its impressions on only a 2.8-position slip, which is the difference between sitting in the answer-box zone and sitting below it.
  • The pattern is mid-funnel utility content. Planner and tool pages, how-to guides, and app/subscription pages. The template gallery, the head terms and the homepage's rank all held. Whatever happened did not touch the top or the long tail — it hit the middle.
  • Both devices, desktop worse. Desktop impressions −27.4% (position 9.41→11.36), mobile −24.9% (7.26→8.26). This is not a mobile-specific answer-engine story.
  • The remaining 45% is a different problem. Several pages improved rank and still lost impressions — /blog/how-to-draw-a-blueprint/ went 10.1→3.9 with impressions down 27%. That residual is answer-engine compression and seasonality, and no amount of page-level work reverses it.
  • Seasonality cannot be isolated. Late July is plausibly a trough for home-project search, but the Feb 17 tracking floor means there is no year-over-year baseline to test against. This is the first summer the data can be trusted.

Why this matters for the plan: a uniform algorithmic squeeze offers nothing to act on. Nine named URLs losing 5–22 positions each is a work list. Q3 Objective 2's Key Page UX Update (10 high-traffic feature/landing pages, owner Trude, due Sep) is aimed at exactly this shape of page — /features/draw-floor-plans/, /features/roomsketcher-app/ and /kitchen-planner/ all qualify. That target list was drawn up before this analysis existed and should be checked against this table.

Tested — Answers a Likely Question

No, Paid Is Not Cannibalising Organic

Paid Search rose 32% in the same window organic fell 16%, which invites the obvious question: are we simply buying traffic we used to get free? Tested four ways, the answer is no — with one small, real exception.

  • The correlation reverses once you remove the trend. Raw weekly paid vs organic correlates −0.47, which looks like substitution — but any two series with opposite trends do that. On week-over-week changes (which strips the trend) the correlation is +0.20, and the two moved in the same direction in exactly 10 of 20 weeks. That is a coin flip. Real substitution would sit close to zero same-direction weeks and a strongly negative coefficient. A lagged test — does a paid surge suppress organic the following week? — returns −0.06, indistinguishable from nothing.
  • The organic decline started before paid scaled. Organic was already down ~20% by mid-May (weeks 19–21). Paid did not scale until weeks 21–24. The cause cannot follow the effect.
  • Cutting paid did not bring organic back. In the week of June 21 paid collapsed to 1,591 sessions — the lowest of the 21 weeks — and organic also fell, to 8,472. When paid peaked at 4,190 in the week of July 19, organic barely moved. The two are simply not connected.
  • The one genuine exception is branded. Branded organic clicks fell 6.2/day while branded paid clicks rose 5.2/day — close to a 1:1 swap, which is exactly what own-brand ads do to own-brand listings. But it is 0.6% of the 1,001 daily organic clicks, nowhere near enough to explain a 16% decline. It does raise a separate question worth asking: the Branded campaign buys ~183 clicks/day at $380/day while branded organic delivers ~83 clicks/day for free, and it is the only campaign clearing ROAS 1.0 (1.09). How much of that would arrive anyway is a genuine unknown and a clean brand-holdout test would settle it.

The harder read: a straight trade would at least be neutral — total sessions flat, cost shifted. That is not what happened. Total US sessions fell 2.4% (4,459→4,350/day) while combined paid spend rose $429/day. Paid did not take organic's traffic; it partially and expensively backfilled an organic decline that has its own separate cause. Two independent problems, not one trade-off.

Context — For the Unexplained 45%

There Is No Labelled Update to Point At

For the portion of the decline that page-level work cannot explain, there is no named event to blame or wait out. Google confirmed on July 9 that smaller core updates now roll continuously without public announcement, and third-party volatility trackers recorded sustained movement through June and July with no official label. There was no announced core update in July 2026. The practical consequence: no rollout end-date, no recovery event to expect, and CTR-at-stable-position becomes its own metric to watch. It is also the part of the problem that argues for answer-surface presence over incremental blue-link optimisation.

Inside Direct Traffic (US)

Direct is 51.3% of US sessions and converts at 9.5% to sign_up — roughly 4.7× the Organic Search rate (2.0%). A cold-traffic channel does not behave that way. It is overwhelmingly returning users and app-adjacent sessions where GA4 kept the user but lost the source. But this cycle's daily data shows it is not purely a retention signal either.

New — Watch

Direct Rises and Falls With Paid Spend (r = 0.80)

The channel chart shows Direct peaking in the week of July 20 and dropping sharply the following week. The daily data explains it, and the explanation matters for how paid budget decisions get evaluated.

DateDirect sessionsSearch-NORAM spendWhat happened
Jul 13–17 (Mon–Fri)2,378/dayNormal baseline
Jul 21–232,965 / 3,566 / 3,11216,817 / 16,822 / 16,847 NOKDirect spikes on exactly the three days paid spend was pinned at its cap
Jul 27–31 (Mon–Fri)1,969/day593–3,082 NOKBudget cut ~85%; Direct falls with it
  • The correlation is strong. Across July 20 – August 2, daily Direct sessions and daily Search-NORAM spend correlate at r = 0.80 (0.84 within the spike window itself). Direct is not behaving as an independent channel.
  • Part of the drop is genuine, not just spike reversion. Comparing like-for-like weekdays and stripping the spike, Direct still fell 17.2% (2,378→1,969/day). Weekend-to-weekend, removing the day-of-week effect entirely, it fell 22.2% (Jul 18–19 vs Aug 1–2).
  • It is not a data artefact. GA4 weeks start Sunday, and the week of July 26 contains all seven days — the decline is real, not a truncated final week.
  • The implication for budget decisions: if a meaningful slice of Direct is paid-driven — users who click an ad, don't convert, and return later without a tracked source — then cutting paid costs more than the paid reports show, because the Direct that follows it goes too. Conversely, paid's true contribution is understated. This deserves a proper test before the next budget decision, not an assumption in either direction.
  • Caveat: correlation over 14 days is suggestive, not conclusive. The tail weakens it — spend recovered on August 1–2 while Direct kept falling — and normal summer seasonality is also in play. Treat it as a strong signal worth investigating.

AI Search Is a Real Channel Now (US)

AI referral traffic — sessions arriving from an AI assistant's answer — fell 15.1% against the baseline and 26.8% against the last reported period. The LLM Visibility Score slipped on both anchor queries over the same stretch, but by less — and RoomSketcher is still the outright #1 recommendation on three of six engines, including the one that sends 78% of the traffic.

AI Sessions / Day
25.2
−15.1% vs baseline
ChatGPT Share of AI
78%
276 of 353 sessions
AI → Signup Rate
4.8%
2.4× Organic Search
AI Share of Sessions
0.6%
336 of 60,898
EngineLast Reported
Jun 15 – 28
Baseline
Jul 6 – 19
Current
Jul 20 – Aug 2
Δ vs Baseline
ChatGPT (chatgpt.com)404324276−14.8%
Perplexity (both sources)304429−34.1%
Gemini (gemini.google.com)293128−9.7%
Claude (claude.ai)8511+120.0%
Copilot (copilot.com)11129−25.0%
Total AI Referral Sessions482416353−15.1%
Totals are 14-day session counts, US only. Perplexity sums perplexity.ai and perplexity. bing and cn.bing.com are counted as Bing organic, not AI.
Watch — The Central Question

AI Clicks Fell Further Than AI Standing Did

AI referral sessions dropped 15.1% while the LLM Visibility Score slipped only 8.3 and 4.2 points on its two anchors — and RoomSketcher is still the outright #1 recommendation on ChatGPT, Perplexity and Copilot. The traffic is falling faster than the ranking, which points at in-line answering absorbing clicks rather than at losing the recommendation.

  • The engine that matters most is unchanged. ChatGPT drives 78% of AI referral traffic and scored a clean 1.0 on both queries, yet sent 15% fewer sessions. Being recommended and being clicked are decoupling.
  • Branded demand is holding, which is the tell. Branded queries fell only 6% (89.1→82.9 clicks/day) against a 17.2% non-brand decline. Users are still arriving with the name in mind — consistent with assistants delivering the recommendation without the click, and with Direct holding at 51% of sessions and a 9.5% signup rate.
  • The measurement gap is now the constraint. Referral sessions understate AI influence, and the Copilot citation export — the one source that would show grounding volume as distinct from clicks — was not pulled this cycle. Until it is, the channel's real contribution cannot be sized.
Positive

AI Traffic Converts 2.4× Better Than Organic Search

The GA4 “AI Assistant” channel produced 16 sign_up events on 336 sessions — a 4.8% signup rate, against Organic Search's 2.0% (310 signups on 15,430 sessions). AI-referred visitors arrive pre-qualified: the assistant has already answered "which tool should I use," so the visit is a decision confirmation rather than a comparison. The volume is small, but per-session it is the highest-intent non-branded traffic on the site.

Note — Engine Detail

ChatGPT Dominates; Claude Is the Only Riser

ChatGPT alone is 78% of AI referral traffic, so total AI volume is effectively a ChatGPT metric — concentration risk worth naming. Claude more than doubled (5→11 sessions) but off a base small enough that two weeks of noise could explain it; worth watching rather than acting on. Perplexity's 34% decline is the sharpest fall and is the one engine where the June reading showed a genuine ranking weakness on the “software” phrasing.

LLM Visibility Score — the Objective 3 KR (NYC — fresh reading, August 3)

Two fixed anchor queries run across six engines on a New York VPN, in fresh/temporary chats so conversation memory cannot bias the answer. Each cell is scored 0–1: 1.0 = definite #1 / best-overall, 0.75 = wins a named sub-category while another tool or nothing holds the overall slot, 0.5 = listed among the recommendations, 0.25 = mentioned or cited but not recommended, 0 = absent. This is the fourth reading; the first was June 1.

“best floorplan software”
87.5%
5.25 / 6 · was 95.8% (−8.3 pts)
“best floor plan creator”
95.8%
5.75 / 6 · was 100% (−4.2 pts)
Engines at 1.0
3 of 6
ChatGPT, Perplexity, Copilot
Queries Measured
4
2 anchors + 2 spelling variants
Engine“floorplan software”
Jun 29
“floorplan software”
Aug 3
“floor plan creator”
Jun 29
“floor plan creator”
Aug 3
What the answer said this reading
ChatGPT1.01.01.01.0“Best overall: RoomSketcher” in both. Creator answer ranks it 🏆 #1, “Overall best.”
Perplexity1.01.01.01.0“Best overall for most users” / “If you want the best all-rounder: RoomSketcher.”
Copilot1.01.01.01.0#1 under a “Best Overall Picks” header; cites “ranked #1 by multiple 2026 reviews.”
Gemini1.00.751.01.0Creator: “1. Best Overall & For Real Estate: RoomSketcher.” Software: slips to #2, winning “Best for Real Estate & Interior Design.”
Claude0.750.751.00.75Refuses an overall winner by design (“the ‘best’ lists are almost all vendor-owned content”). Gives RoomSketcher the real-estate / listing-plans category outright in both.
Google AI Mode1.00.751.01.0Creator: “The absolute best floor plan creator software overall is RoomSketcher.” Software: 2nd of three named, leads “Advanced and Professional Software.”
Total5.755.256.005.7587.5% and 95.8% respectively
Watch — Modest Decline

Both Anchors Slipped, but RoomSketcher Is Still the Default Recommendation

“Software” fell 8.3 points and “creator” 4.2. Three engines — ChatGPT, Perplexity and Copilot — returned a clean 1.0 on both queries, and ChatGPT alone drives 78% of AI referral traffic, so the commercially dominant surface is fully intact. The slippage is two single-step moves: Gemini and Google AI Mode each dropped from “best overall” to “best for real estate / professional” on the software phrasing.

  • The pattern is consistent, not random. Where RoomSketcher loses the top slot, it always retains the real-estate / professional-output category — in every one of the six engines, across both queries. That is a durable, defensible position and it matches the product's actual strength.
  • “Creator” remains the stronger term (95.8% vs 87.5%), as it has been in all four readings. Notably this is the exact inverse of the GSC picture, where RoomSketcher ranks 6.9 on “floorplan software” but 21.0 on “floor plan creator.” The LLMs and the blue links disagree about which term the brand owns — and the LLMs are backing the term the new /floor-plan-creator/ page was built for.
  • Claude names the competitive mechanism. Both its answers flagged that RoomSketcher's own “8 Best Floor Plan Software Tools” post was updated July 15 and currently ranks top for the term, while Matterport has refreshed a competing February piece. On the creator variant it was blunter: “RoomSketcher doesn't own it” — the omnibus blog post is competing against Planner 5D's purpose-built /use/free-floor-plan-creator landing page and a DeskFlex roundup segmenting by use case (offices, classrooms, restaurants, weddings).
Methodology — New This Cycle

Google AI Mode Is Not Reproducible Run-to-Run

AI Mode was captured twice per query this cycle, minutes apart, in identical conditions. The answers were not variations on a theme — they were different recommendation sets. On “software” the first run omitted RoomSketcher from all four categories (scoring 0.25) and the second placed it second of three named tools (0.75). On “creator” the first gave Floorplanner the “Best Overall for Beginners” slot (0.75) and the second opened with “the absolute best floor plan creator software overall is RoomSketcher” (1.0).

  • A single AI Mode capture is not a measurement. The scores above use the later run for both queries. Going forward AI Mode should be captured three times and scored on the median — the other five engines have been stable across all four readings and need only one run.
  • This retires a finding. An earlier draft of this issue reported a sharp Google-driven collapse. That was one unstable draw, not a trend, and it does not survive the re-capture. Flagged here because the correction matters more than the original claim.
New — Spelling Variants Measured

“Floorplan” vs “Floor Plan”: Google Normalises, Copilot Doesn't

All four spelling permutations were captured this cycle (24 answers total), which allows a direct test of whether the one-word/two-word distinction is real. It is — but only on some engines.

QuerySpellingScoreStatus
best floorplan softwareone word87.5%Locked anchor — trends from June 1
best floor plan creatortwo words95.8%Locked anchor — trends from June 1
best floor plan softwaretwo words87.5%New series — baseline set this issue
best floorplan creatorone word87.5%New series — baseline set this issue
  • Google AI Mode returned a word-for-word identical answer to both software spellings — same three names, same four category headings. Google normalises the variants internally.
  • Copilot does not. On “floor plan creator” it named RoomSketcher the outright best (1.0); on “floorplan creator” it gave “Best overall” to Homestyler and RoomSketcher only “Easiest to use” (0.75). Same engine, same day, spelling the only variable.
  • Claude explained why the variants diverge: “'creator' pulls a noticeably different intent — it skews free, browser-based, and consumer, where 'software' skews pro and CAD-adjacent.” That is a content-strategy instruction, not just a measurement note.
  • Search volume backs the two-word form decisively — 604k US impressions vs 48k over 90 days, a 12.7:1 ratio. The two-word variants are now tracked alongside the locked anchors so the KR follows the language buyers actually use.

Keyword Expansion Opportunity (US)

The head terms improved this cycle — in several cases substantially. That makes the traffic decline easier to diagnose and the remaining gaps more valuable: the terms RoomSketcher still has no dedicated page for are the ones where competitors and AI-native entrants are unopposed.

US Impression Volume by Term Family — Current Window (daily avg)
“floor plan”
123/day · pos 7.4
“room planner”
57/day · pos 20.7
“...software”
43/day · pos 8.8
“...creator”
37/day · pos 21.0
“...app”
32/day · pos 8.9
“free ...software”
30/day · pos 5.5
“...maker”
19/day · pos 24.1
“floorplan software”
19/day · pos 6.9
Positive — Action Completed

The /floor-plan-creator/ Page Shipped

A dedicated /floor-plan-creator/ page is now live — titled “Floor Plan Creator – The Easiest Way to Make Floor Plans,” with a clean H1, a proper meta description referencing AI-powered tools, and a full page build. This closes a gap that had been open across every prior issue.

  • Early indexing signal is good. Daily impressions went from 5.8/day in the baseline to 29/day in the current window — a 5× increase in two weeks.
  • It has not started ranking yet. Average position is ~35 and clicks are 1.6/day. Google is testing it broadly (impressions up) without committing to a position. This is the normal shape of a new page's first month; the read-out that matters is next cycle.
  • Watch for a temporary head-term dip. The query “floor plan creator” moved from position 18.7 to 21.0 this cycle. A new page competing with existing pages for the same term commonly causes a short consolidation wobble before it resolves.
Critical — Carried Forward

“Floor Plan Maker” Still Has No Page — and Now Has an AI-Native Competitor on the Exact Domain

Verified this cycle: /floor-plan-maker/, /floor-plan-app/, and /ai-floor-plan-generator/ all return 404. RoomSketcher ranks 24.1 on “floor plan maker” on the strength of unrelated pages alone. Meanwhile floorplanmaker.ai now exists as an exact-match AI-native domain on that term. The “creator” page took multiple cycles to ship and is already showing a 5× impression lift — “maker” is the same trade at 19 impressions/day of standing demand, and the competitive window on it is closing.

Positive

Head Terms Moved the Right Way Across the Board

Six of the eight tracked head terms improved position this cycle, several sharply: “floor plan” 12.5→7.4, “free floor plan software” 10.1→5.5, “room planner” 29.9→20.7, “floor plan app” 10.0→8.9, “floor plan software” 9.6→8.8. Only “floor plan creator” slipped, and that has a page-consolidation explanation. The domain's authority on its core vocabulary is strengthening even as total clicks fall — which is exactly why the traffic decline should not be read as an SEO failure.

Competitive Landscape

The established competitor set is stable. The change this cycle is underneath it: a cohort of AI-native tools has consolidated around “describe your space in plain English→get a floor plan,” and 2026 round-up content now treats text-to-floor-plan as a baseline expectation rather than a differentiator.

Competitor“Creator” Page“Maker” PageAI FeaturePositioning / Differentiator
RoomSketcherYes — newNo (404)YesProfessional results, beginner-friendly; deep template gallery; real-estate and listing workflows
CedreoYesNot AI-brandedHome builders, contractors, remodelers. “Draw a complete house in 2 hours.” Room-specific planners (kitchen, bathroom, basement)
Planner 5DYesYesYesFree tier + consumer-friendly; cited in 2026 AI round-ups as a free AI option
FloorplannerYesYesPartialVolume/embed play for real estate portals
SmartDrawYesYesPartialDiagramming breadth; strong exact-match SEO footprint
SketchUpPartialProfessional 3D modelling; architect/designer end of the market
floorplanmaker.aiExact-match domainNativeNew entrant. Free text-to-floor-plan generator on the exact term RoomSketcher has no page for
Maket.aiNativeNamed top residential AI generator in 2026 round-ups
SnaptrudeNativeText brief → LOD 300–350 BIM, exports to Revit. Professional/architect end
Watch — New Entrants

AI-Native Tools Are Competing on Vocabulary RoomSketcher Owns but Doesn't Defend

The new cohort — floorplanmaker.ai, Maket.ai, ArchyBase, Snaptrude, TestFit, Finch3D, RoomGPT — is not currently taking RoomSketcher's rankings; the head terms improved this cycle. The threat is narrower and more specific: these tools are building their SEO and their LLM presence on “AI floor plan generator” and “floor plan maker”, and RoomSketcher has no page on either. When an assistant assembles a recommendation set for “AI floor plan generator,” there is nothing on roomsketcher.com built to be cited for it — despite the product having AI features and the new creator page's own meta description advertising them.

Watch — Competitive Intel from the LLM Capture

Competitors Are Explicitly Contesting RoomSketcher's “Best Overall” Framing

Both Claude responses in this cycle's LLM Visibility capture volunteered unprompted competitive detail worth acting on. Matterport published an “8 Best Floor Plan Software” piece in February and refreshed it days before this reading; Claude characterised its framing as deliberately anti-listicle — arguing there is rarely one best tool, only the best tool for a specific job — which it described as “a smart wedge against RoomSketcher's own 'RoomSketcher is best overall' positioning on the same keyword.” Space Designer 3D and My Site Plan are running comparison plays on the same term.

  • This is the mechanism behind the Objective 3 KR decline. The engines that dropped RoomSketcher (Google AI Mode) and the one that refuses to name an overall winner (Claude) are both being fed by content built specifically to dissolve the "best overall" frame.
  • RoomSketcher's own comparison post was refreshed mid-July, per Claude — so the defence is already in motion. Worth confirming that refresh is reflected in what the engines are retrieving.
  • The counter is category ownership, not overall-best claims. Every engine that scored RoomSketcher below 1.0 still gave it the real-estate / listing-plans category outright. That is a defensible, specific position; "best overall" is the contested one.
Note

Cedreo Is Unchanged — Still Professional-Only, Still Not AI-Branded

A spot-check of Cedreo's homepage this cycle found no AI-branded features and no new product launches. Positioning remains squarely on home builders, contractors, remodelers and interior designers — the professional segment — with speed as the core claim. Cedreo is not currently contesting the homeowner/DIY end where RoomSketcher's gallery and free tier compete, and it is not yet using AI as a wedge. That leaves the AI framing available to whoever claims it first.

What's Working Well (US)

Four things held or improved this cycle against a broadly negative backdrop. Each is worth protecting explicitly, because in a down cycle the instinct is to change things that are working.

Strength

The Template Gallery Absorbed the Organic Decline Without Losing a Click

Gallery clicks held at exactly 90.6/day across both windows while site-wide organic clicks fell 16.5%, and the number of gallery pages earning clicks rose from 157 to 166. With 832 pages drawing impressions, this is the most resilient organic asset on the property. It is the single clearest argument for continuing to invest in gallery depth — it is the part of the site that did not decline.

Strength

Google Ads Click-Through Rate Reached 9.84%

Account-level CTR improved from 8.27% (last reported) to 9.84% — a meaningful gain that indicates ad relevance and query matching are getting better, not worse. Clicks rose 34% on the baseline. Whatever is wrong with paid efficiency this cycle, it is not the ads' ability to earn a click. The problem sits downstream, in what those clicks are optimised toward.

Strength

Microsoft Ads Cost per Conversion Improved 10%

Microsoft's blended cost per conversion fell from $12.82 to $11.50 as spend was cut 33%. Two campaigns improved materially: Branded NORAM CPA $138→$93, and Competitors NORAM $296→$227 — the latter still expensive but moving the right way. The pullback was executed cleanly on the efficiency metric; the cost was volume, particularly in subscriptions.

Strength

Demand Held While Acquisition Wobbled

begin_checkout rose 1.3% and sign_up fell only 3.1% — against a 16% organic session decline. All-source sign_up is still 11% above the last reported period (274→304/day). The top of the funnel narrowed but intent-to-buy did not, which suggests the underlying product demand is intact and this is a traffic-and-efficiency problem rather than a market problem.

Site Performance & Homepage

The PageSpeed Insights API quota was exhausted again this cycle — the second consecutive issue — so Lighthouse was run locally instead. This produces real, current measurements, but under materially more favourable lab conditions than PSI's throttled environment. Read the numbers below as a fresh absolute read, not as a trend against Issues #1–#7.

Methodology — Read This First

These Numbers Are Not Comparable to Previous Issues

Issues #1–#7 reported PageSpeed Insights values (most recently mobile Performance 60, mobile LCP 13.1s, carried forward unverified since June 15). This issue reports local Lighthouse 12 runs on an unthrottled Mac over a residential connection. That environment is much faster than PSI's simulated mid-tier mobile device, so the scores are structurally higher and a comparison between them would be meaningless. No delta is shown for that reason. What these runs can establish is the current absolute state and, more usefully, the variance.

Mobile Performance
84
median of 4 · range 66–93
Mobile LCP
4.01s
median of 4 · range 2.88–10.85s
Desktop Performance
94
avg of 2 · range 93–95
Desktop LCP
1.48s
avg of 2 · range 1.31–1.65s
Accessibility
97
both form factors
SEO
100
both form factors
Best Practices
78
mobile 79 · desktop 78
CLS
0.03
well inside “good”
Critical — Mobile

Mobile LCP Ranged From 2.88s to 10.85s Across Four Identical Runs

The variance is the finding. Four runs of the same URL, same machine, minutes apart, produced Performance scores of 66, 87, 93 and 81 and LCP values of 10.85s, 3.29s, 2.88s and 4.72s. A stable site does not do this. It means some mobile visitors are getting a genuinely fast homepage and others are waiting three to four times longer, and which one you get appears close to random.

  • The LCP element is the hero image served from wpmedia.roomsketcher.com — a separate host from the main domain, which adds DNS + TLS negotiation before the largest element can even begin downloading.
  • Lighthouse's top opportunity is 1,220ms of unused JavaScript, followed by 566ms recoverable from preconnecting to required origins — and the missing preconnect points directly at that image host.
  • Server response time is not the problem (flagged as already short). This is a front-end delivery issue on the critical path, which is WordPress-side and therefore within our control.
  • Even at the favourable local median of 4.01s, mobile LCP is outside Google's 2.5s “good” threshold. On PSI's throttled profile it would be materially worse.
Process Risk

PageSpeed Quota Has Blocked Trended Speed Data for Two Cycles Running

The PSI API returned a daily-quota error on both the keyed and unkeyed endpoints during this run, exactly as it did on June 29. The consequence is that the mobile-speed regression first flagged in Issue #5 has now gone two full cycles without a comparable measurement, and the 13.1s figure still being carried in prior issues is nine weeks stale. Local Lighthouse is a usable stopgap but it cannot rebuild the trend line. Re-running PSI early in the next cycle, before the daily quota is consumed, is the only way to restore a comparable trend line.

What Needs Help (US)

Five items below are new or materially changed this cycle. The paid-efficiency finding is first because it is the largest controllable sum of money on the table, and because it resolves to a specific campaign on specific dates rather than a diffuse "auction got harder" story.

Critical — Root Cause

Every Campaign Is Told to Deliver a ROAS Below the OKR Target

All four NORAM campaigns run Maximize Conversion Value with an explicit target ROAS. Not one target is set at or above the 1.0 the Q3 KR requires:

CampaignTarget ROASActual ROASDaily BudgetImpr. ShareLost to Budget
0. S – Branded0.941.09$1,63879.9%0.0%
2. S – Competitors0.740.68$52818.0%5.8%
3. P-Max0.740.68$13614.8%8.6%
1. S – Search0.800.27$22817.4%26.6%
Combined US (incl. Microsoft)0.6031.8%

Smart Bidding is doing what it was told. Hitting the OKR requires changing the instruction, not the execution — the targets are the KR, expressed in the only place the algorithm reads.

Correction — Supersedes an Earlier Read

The July 24 Budget Cut Was Probably the Right Call, Not a Mistake

An earlier draft of this issue flagged 1. S - Search - NORAM as money left on the table: it was pinned at ~$1,530/day on July 21–23 at $5.78–$8.13 per conversion — the best CPA in the window — then collapsed to $54–$204/day. Conversion-value data inverts that reading.

  • That campaign has the worst ROAS in the account (0.27) against its own 0.80 target. Its CPA looked excellent only because CPA counts free accounts, which carry a conversion value of roughly 1.6 NOK each. A new subscription is worth ~1,404 NOK — about 860× more. Free accounts are 93% of Google's paid conversion count but 2% of its conversion value.
  • The collapse was a configuration change, not an auction effect. The campaign's configured budget is now $228/day; it spent ~$1,530/day on July 21–23, which is 6.7× that. Google cannot overspend a daily budget by 6.7×, so the budget was cut roughly 85% around July 24–27. Budget-lost impression share confirms the squeeze from both sides: 37–66% on July 21–24 while spending hard, and 76% on July 30 after the cut.
  • Read plainly: someone throttled the account's worst-returning campaign. On the KR that Q3 actually measures, that improved things. The open question for Action #2 is no longer “why was it throttled” but “was it deliberate, and is the same value-based scrutiny being applied to Competitors and P-Max, which sit at 0.68?”
Critical — Worsening

Cost per Paid Subscription Rose 33% Across Both Engines

Combined Google + Microsoft spend rose 28% ($1,555→$1,984/day) while combined new subscriptions fell 4% (9.12→8.75/day), taking cost per paid subscription from $171 to $227. The two engines failed differently and neither offset the other:

  • Google scaled and got worse per unit. Spend +63%, subscriptions +16%, cost per subscription $161→$225 (+40%).
  • Microsoft cut and lost more than it saved. Spend −33%, subscriptions −46%, cost per subscription $189→$234 (+23%). Blended CPA improved, but subscription economics deteriorated — the cuts landed on volume that was paying its way.
  • 94% of Google's paid conversions are free accounts. With free signups (1,832) dwarfing subscriptions (99.5), Smart Bidding optimises toward the abundant cheap event. This is the conversion-goal pollution flagged since Issue #1 — it is no longer a theoretical tidiness problem, it is actively steering spend toward the wrong outcome.
Critical — New

88% of Subscription Revenue Events Have No Channel Attribution

Of 232 new_subscription events in the current window, 205 landed in GA4's “Unassigned” channel — along with 212 of 432 purchase events — on just 1,172 sessions. Direct received 16, Paid Search 6, Organic 4, AI 1. In practice this means GA4 currently cannot answer "which channel drives paid subscriptions," which is the single question that matters most for budget allocation.

  • The pattern (huge conversion counts on few sessions) is the signature of conversions fired for returning/logged-in users where GA4 retained user_id but lost session source — most likely a cross-domain or app-handoff gap between the WordPress site and the Flutter app.
  • It is getting worse, not better: Unassigned new_subscription rose from 187 to 205 between windows.
  • Every channel ROI figure in this report understates paid and organic by a structural margin because of it. The scorecard's Google/Microsoft subscription numbers come from the ad platforms directly, which is why they remain usable — but they cannot be reconciled against GA4 while this persists.
Watch — Revised This Cycle

Organic Is Two Problems, and Only One of Them Is Unfixable

Section 2 splits the five-month decline into its parts. The split matters because it changes what to do about it.

  • The larger part is recoverable. Nine pages lost 5–22 positions each and account for 55% of the decline. That is a diagnosable work list — audit what changed on those URLs, what now outranks them, and whether the Q3 Key Page UX Update covers them.
  • The smaller part is not. Pages that improved rank still lost ~20–27% of impressions. That residual is answer-engine compression and seasonality, and no amount of optimisation reverses it. It is the part that argues for AEO and answer-surface presence over incremental blue-link work.
  • The gallery is the control group. It held clicks flat at 90.6/day through the whole decline. Long-tail template pages appear structurally insulated from whatever hit the utility pages — which supports funding Q3's FPG initiatives.
  • Branded demand is the durable asset. Branded queries fell 6% against a 17.2% non-brand decline. Anything that grows brand recall compounds where SERP clicks no longer do.
Carried Forward — Still Open

Longer-Horizon Gaps, Unchanged This Cycle

These were open at Issue #7. The Q3 OKRs pick up two of them directly, which is worth noting explicitly — they move from "gap" to "scheduled."

  • No retargeting — now scheduled. Q3 Objective 1, Initiative 2 (Remarketing Setup, owner Wida, due August) covers Meta remarketing for both "Hot" (signed up) and "Warm" (visitors) audiences. With 51% of traffic arriving via Direct and converting at 9.5%, this is the best-evidenced item on the paid objective.
  • Long-tail blog decay — now scheduled. Q3 Objective 2, Initiative 1 (Old Blog Article SEO, owner Trude, contributor Kworq, due August) adds FAQ/ToC structure to 300 older articles. Blog pages lost 16% of clicks this cycle, so the timing is right — and structured markup is also what makes a page quotable by an answer engine.
  • No Reddit or Quora presence — still open, and now more consequential. Both are heavily weighted in AI citation, and Google AI Mode's "software" answer this cycle cited Reddit threads for three of its four categories while citing roomsketcher.com only for a support article.
  • No free-tool strategy — still open. The AI-native cohort leads with free generators as an acquisition wedge; RoomSketcher leads with a free tier behind a signup.
  • German non-brand search waste and unpublished GTM tags — both previously flagged, neither confirmed resolved.

Market Context

Two external shifts frame everything above: search is resolving more queries without a click, and text-to-floor-plan generation has become a table-stakes feature rather than a novelty.

Google Core Updates
Continuous
Unannounced since July 9, 2026
Text-to-Floor-Plan
Standard
Baseline feature in 2026 round-ups
AI Signup Rate
4.8%
vs 2.0% organic search
Organic vs March Peak
−37%
Weekly US sessions
Trend

The Industry Has Standardised on Natural-Language Input

2026 comparison content now treats "describe your space in plain English and get a to-scale plan" as an expected capability, alongside sketch-to-plan and photo-to-plan. Tools are differentiating on what happens after generation — Snaptrude on BIM/Revit export, TestFit on multi-family feasibility, ArchyBase on connecting plans to rendering and 3D. RoomSketcher's genuine differentiators (template depth, real-estate listing workflows, professional output from a beginner-friendly editor) are durable, but they are increasingly hard to discover through AI answers if the site has no page that speaks the AI vocabulary.

Trend

Unannounced Continuous Updates Change How to Respond to Volatility

Google's July 9 confirmation that smaller core updates now roll without announcement removes the old playbook of "wait for rollout to finish, then assess." There is no rollout end-date and no named update to recover from. The practical adaptation is to monitor CTR-at-stable-position as its own metric — which is precisely the pattern visible in this cycle's data — and to treat answer-surface presence as the hedge against it.

Next Steps Before Next Call

Six items for the next 14 days, ordered so the diagnostics and confirmations that unblock everything else come first. Items marked KWORQ are ours to execute. Objective tags map each action to the Q3 OKR it serves.

OBJ 1Recommended — Raise Every Target ROAS to at Least 1.0

All four NORAM campaigns run Maximize Conversion Value with an explicit target ROAS set below the Q3 KR: Branded 0.94, Search 0.80, Competitors 0.74, P-Max 0.74. The account is delivering 0.60 because that is roughly what it was asked for. Our recommendation is to raise the targets toward 1.0 in staged increments rather than in one step — Smart Bidding needs a learning window and volume will dip before efficiency recovers — starting with Competitors and P-Max at 0.74. Branded is already returning 1.09 and is best left alone. Happy to model the likely volume trade-off at each target level if that would help the decision.

Owner: RoomSketcher (Wida)  ·  Kworq: can model the volume/return trade-off on request  ·  Outcome: Bidding aimed at the KR instead of below it.

OBJ 1Confirm the July 24 Budget Cut on Search NORAM Was Deliberate

1. S - Search - NORAM went from ~$1,530/day to a configured $228/day around July 24–27 — an ~85% cut. On ROAS that was the right move (the campaign returns 0.27, the worst in the account). We need to know whether it was an intentional response to poor return or an unrelated budget action, because it determines whether the same value-based scrutiny is already being applied to Competitors and P-Max, both sitting at 0.68.

Owner: RoomSketcher (Wida)  ·  Outcome: Confirms whether budget decisions are being made on value or on volume.

OBJ 1KWORQ — Fix Subscription Attribution in GA4

88% of new_subscription events land in "Unassigned." Trace where session source is lost between the WordPress site and the Flutter app — most likely a cross-domain linker or app-handoff gap — and restore channel attribution on revenue events. Note the scope: per-engine ROAS is measurable from platform data (Section 0), so this does not block the Objective 1 KR. What it blocks is comparing paid against organic and AI on the same basis — which is what the budget-allocation decision actually needs.

Owner: Kworq  ·  Outcome: Subscription revenue attributable to channel; paid ROI measurable in GA4 rather than platform-only.

OBJ 3KWORQ — Lock the Expanded LLM Visibility Method for Objective 3

Objective 3's KR needs a measurement method robust enough to score against. Three changes, all evidenced this cycle: capture Google AI Mode three times per query and score the median (two runs minutes apart produced different recommendation sets); track all four spelling variants rather than two, since Copilot ranks the one-word and two-word forms differently and the two-word form carries 12.7× the search volume; and verify the query string in every screenshot before scoring. Baselines for all four are set in Section 3.

Owner: Kworq  ·  Outcome: An Objective 3 KR that moves for real reasons rather than sampling noise, measured on the language buyers actually use.

OBJ 2Publish the /floor-plan-maker/ Page

The creator page shipped and produced a 5× impression lift within two weeks. "Floor plan maker" carries 19 impressions/day of standing demand at position 24 with no dedicated page behind it, and floorplanmaker.ai now holds the exact-match domain. Same trade, same evidence, one term over.

Owner: RoomSketcher  ·  Outcome: A ranking asset on the second-largest uncovered head term, before the AI-native entrant consolidates it.

OBJ 2OBJ 3Decide Whether to Build an “AI Floor Plan Generator” Page

The product has AI features — the new creator page's own meta description says so — but /ai-floor-plan-generator/ is a 404 and nothing on the site is built to be cited when an assistant assembles recommendations for that phrasing. This is the term the entire new competitive cohort is organising around. The decision needed this cycle is whether to claim it; the build itself can follow.

Owner: RoomSketcher  ·  Outcome: A position on the fastest-growing query family in the category, or an explicit decision to cede it.

Terms Used in This Report

TermMeaning
SEOSearch Engine Optimisation — earning visibility in conventional search results.
AEOAnswer Engine Optimisation — being the source an AI assistant cites when it answers directly.
GEOGenerative Engine Optimisation — shaping how generative AI systems represent and recommend a brand.
GSCGoogle Search Console — source for impressions, clicks, CTR and average position.
LCPLargest Contentful Paint — time until the largest visible element renders. Google's "good" threshold is 2.5s.
CLSCumulative Layout Shift — how much the page moves while loading. Below 0.1 is "good".
TBTTotal Blocking Time — how long the page is unresponsive to input during load.
CTRClick-Through Rate — clicks divided by impressions.
CPCCost per Click.
CPACost per Acquisition — spend divided by conversions. In this report, "blended" CPA counts all conversion actions including free accounts.
P-MaxPerformance Max — Google's automated campaign type spanning Search, Display, YouTube and Shopping inventory.
UnassignedGA4's bucket for sessions where the traffic source could not be determined — see Section 8.