Home Station → Journey → Dabbo 11 📈 → 11.5

📈 11.5 — SEO Live Report — Universal SOP (koi pan client / project mate)

Dabbo 11 · Client Reporting System ·

Aa SOP ma Client A Products no report jem banavyo, e j flow step-by-step lakhyo chhe. Navo client hoy to aa j order ma follow karo: Setup → Data → Analysis → Content → Build → QA → Deploy.


11.5.A 0. Akho flow ek nazar ma

[Client profile]  →  [GSC data: 7 / 28 / 90 days]  →  [GA4 Organic data] ↓                       ↓                              ↓ [Site live audit: top 10 pages]  →  [Analysis rules: what changed, striking, low CTR] ↓ [Rewrites + New ideas + Fixes (data na reason sathe)] ↓ [Website build: Next.js (live) ane/athva HTML artifact (snapshot)] ↓ [QA checklist]  →  [GitHub → Vercel]  →  [Client ne link]

Be output banave chhe:

OutputShu chheKyare vaparvu
Live website (Next.js + Composio + ChatGPT)Data darek var khulta j live aave chhe, 7/28/90 days buttonsLong-term, darek mahine report banavvo na pade
Snapshot artifact / HTMLAaj na saacha numbers HTML ma fixTurant client ne batavvu hoy, ke Composio connect na hoy

11.5.B 1. Golden rules (kyarey todvana nahi)

  1. Ek pan number banavvano nahi. Darek number GSC ke GA4 mathi j aavvo joie. Dummy/demo data hoy to page par upar mota akshar ma "DEMO DATA" lakho.
  2. Saachu account check karo. Composio / Chrome je Google account thi connected chhe ema client ni property chhe ke nahi, e pehla check karo (Client A vakhte connected account ma Client A j na hatu).
  3. $0 revenue hoy to saachu batavo. Revenue 0 hoy to "tracking set nathi" e Fix tarike lakho, khota orders na mukvana.
  4. Period hamesha lakho. Darek table/section ma date range ane comparison range lakho.
  5. Brand keywords alag. Branded ane Non-branded keyword ne mix na karvana.
  6. Content (rewrites/ideas/fixes) ma darek suggestion sathe "Why (data)" reason — impressions, position, CTR na number sathe.

11.5.C 2. Step 1 — Client profile (5 minute)

Navo client hoy to aa table bharo:

FieldExample (Client A)Tamaro client
Client nameClient A Products
Domainclient-a-store.com
GSC propertyhttps://client-a-store.com/ (URL-prefix) athva sc-domain:xyz.com
GA4 property ID558018808 (account 411256034)
PlatformShopify
Client typeEcommerceEcommerce / Lead-gen / Blog / Local
Main marketUSA (usa, gl=us)
Brand termsClient A, sky line
Blog path/blogs/WordPress: /blog/
Collection/category path/collections//product-category/
Product path/products//product/

GA4 property ID kevi rite shodhvu: GA4 kholo → property picker ma client nu naam search karo → URL ma #/a<ACCOUNT>p<PROPERTY>/ dekhashe. p pachhi no number e property ID chhe.


11.5.D 3. Step 2 — Date ranges nakki karo

GSC data ma 2 divas no lag hoy chhe, etle end date = aaj − 2 divas.

PeriodCurrentComparison (same length, just pehla)
7 daysend−6 → endte pehla na 7 divas
28 daysend−27 → endte pehla na 28 divas
3 months (90 days)end−89 → endte pehla na 90 divas

Example (end = 2 Nov 2026): 7d = Oct 27–Nov 2 vs Oct 20–26 · 28d = Oct 6–Nov 2 vs Sep 8–Oct 5 · 90d = Aug 5–Nov 2 vs May 7–Aug 4.


11.5.E 4. Step 3 — GSC data levo

Option A: Composio thi (automatic, live website mate)

  1. Composio ma google_search_console connect karo — je Google account ma client ni property chhe e j account thi.
  2. GOOGLE_SEARCH_CONSOLE_LIST_SITES chalavo → client ni property list ma chhe ke nahi e check karo. Na hoy to navu account connect karo.
  3. GOOGLE_SEARCH_CONSOLE_SEARCH_ANALYTICS_QUERY darek period mate 2 var (current + comparison):

{ "site_url": "https://client.com/", "start_date": "2026-10-06", "end_date": "2026-11-02", "dimensions": ["page"], "row_limit": 1000 }

dimensions ma ["page"], ["query"], ane trend mate ["date"] — ek ek alag call. Note: ctr 0–1 fraction ma aave chhe, display vakhte ×100 karo.

Option B: Chrome browser thi (Composio na hoy tyare — Client A ma aa j vapryu)

  1. Aa URL kholo (resource_id, dates, breakdown badlo):

https://search.google.com/search-console/performance/search-analytics?resource\_id=https%3A%2F%2Fclient.com%2F\&start\_date=20261006\&end\_date=20261102\&compare\_start\_date=20260908\&compare\_end\_date=20261005\&metrics=CLICKS%2CIMPRESSIONS%2CCTR%2CPOSITION\&breakdown=page

breakdown=page → pages, breakdown=query → keywords.

  1. Page khulya pachhi console/JS ma aa extractor chalavo. Ek var FX localStorage ma save karo, pachhi darek page par await eval(localStorage.getItem('FX'))('p28') chalavo:

// Columns: [url/query, clicks, prevClicks, impr, prevImpr, pos, prevPos] (async k=>{ await new Promise(r=>setTimeout(r,3500)); const n=s=>+String(s).replace(/,/g,'').replace('%','')||0; const T=[...document.querySelector('table').rows].slice(1).map(r=>[...r.cells].map(c=>c.innerText.trim())); const b=document.body.innerText; const tot=[...b.matchAll(/(Total clicks|Total impressions|Average CTR|Average position)\n([\d,.K%]+)\n[^\n]*\n([\d,.K%]+)/g)].map(m=>[m[2],m[3]]); localStorage.setItem('R_'+k, JSON.stringify({tot, rows:T.map(c=>[ c[0].replace('https://client.com','').split('?')\[0\].split('\#')\[0\] .replace(' Copy URL to clipboard Open in new tab Inspect URL',''), n(c[1]),n(c[2]),n(c[4]),n(c[5]),n(c[10]),n(c[11]) ]).sort((a,b)=>b[3]-a[3]).slice(0,80)})); return 'ok '+T.length+' '+JSON.stringify(tot); })

Keys: p7 q7 p28 q28 p90 q90 (p = pages, q = queries).

  1. Badho data ek sathe kadhva (JS output 1000 characters par cut thay chhe, etle page par lakhi ne vancho):

const o={};['p7','q7','p28','q28','p90','q90'].forEach(k=>o[k]=JSON.parse(localStorage.getItem('R_'+k))); const p=document.createElement('pre');p.textContent=JSON.stringify(o);document.body.replaceChildren(p);

Pachhi get_page_text thi akho JSON vanchi ne data.json ma save karo.

Dhyan:

  • Compare mode ma column order: 0 page | 1 clicks | 2 prevClicks | 3 diff | 4 impr | 5 prevImpr | 6 diff | 7 ctr | 8 prevCtr | 9 diff | 10 pos | 11 prevPos | 12 diff.
  • #anchor vala duplicate URLs aave chhe → dedupe karo (pehli row rakho).
  • Totals "65K" jem rounded aave chhe — e j rite batavo, "approx" lakho.

11.5.F 5. Step 4 — GA4 data levo

Option A: Composio

GOOGLE_ANALYTICS_LIST_ACCOUNT_SUMMARIES → property check. Pachhi GOOGLE_ANALYTICS_RUN_REPORT:

{ "property": "properties/558018808", "dateRanges": [{"startDate":"2026-10-06","endDate":"2026-11-02"}], "dimensions": [{"name":"landingPage"}], "metrics": [{"name":"sessions"},{"name":"activeUsers"},{"name":"transactions"},{"name":"purchaseRevenue"}], "dimensionFilter": {"filter":{"fieldName":"sessionDefaultChannelGroup","stringFilter":{"value":"Organic Search"}}}, "limit": 500 }

metricValues[].value string aave chhe → number ma convert karo.

Option B: Chrome

  1. GA4 → property picker → client select.
  2. Reports → Engagement → Landing page.
  3. Add filter → Dimension: Session default channel group → exactly matches → Organic Search → Apply.
  4. Date range set karo, rows per page 25/50.
  5. get_page_text thi table vancho: Landing page, Sessions, Active users, Engagement time, Key events, Total revenue.

Check karo: Total revenue ane Key events 0 hoy to → ecommerce tracking set nathi. Report ma "Orders/Revenue: 0 — tracking not set up" lakho ane Fixes ma High priority.


11.5.G 6. Step 5 — Site live audit (top 10 pages)

GSC mathi top impressions vali ~10 pages lo (homepage, top collections, top blogs, low-CTR pages). Client ni site browser ma kholi ne same-origin JS chalavo (server mathi fetch block thay to aa j rasto):

const U=["/","/collections/x","/blogs/news/y"];const out=[]; for(const u of U){const h=await (await fetch(u)).text();const d=new DOMParser().parseFromString(h,'text/html'); const m=d.querySelector('main')||d.body;const imgs=[...m.querySelectorAll('img')]; out.push({u,t:d.title.trim(),tl:d.title.trim().length, md:(d.querySelector('meta[name=description]')?.content||'').trim(), h1:[...d.querySelectorAll('h1')].map(x=>x.textContent.trim()), words:(m.textContent||'').trim().split(/\s+/).length, img:imgs.length,noalt:imgs.filter(i=>!(i.getAttribute('alt')||'').trim()).length, schema:[...d.querySelectorAll('script[type="application/ld+json"]')].map(s=>{try{const j=JSON.parse(s.textContent);return [].concat(j['']||j['']?.map(x=>x[''])).join('/')}catch{return '?'}}), canonical:d.querySelector('link[rel=canonical]')?.href})} const p=document.createElement('pre');p.textContent=JSON.stringify(out);document.body.replaceChildren(p);

Audit checklist (darek page par)

CheckProblem kyarePriority
Title length> 60 ya < 30 chars, ya keyword nathiLow–Medium
Meta descriptionNathi, > 160 chars, ya search intent sathe match nathiMedium
H10 ke 1 thi vadhu, ya keyword vagar nuMedium
Image altAlt vagar ni imagesHigh jo ghani hoy
SchemaBlog ma Article/Breadcrumb nathi · Collection ma CollectionPage/ItemList nathi · Product ma Product nathiMedium
CanonicalNathi ke biji URL par jay chheHigh
Content< 300 words (collection/blog)Medium
GA4 trackingRevenue/Key events 0High
(not set) landing pageGhana sessionsLow

11.5.H 7. Step 6 — Analysis rules (data mathi decision)

Aa rules code ma pan chhe (lib/analyze.js) ane manually pan aa j rite karo:

SectionRule
Blog trafficURL ma /blogs/ ke /blog/ hoy e pages
Other pagesBaki badhi pages (home, collections, products, pages)
Pages gaining clicksclicks − prevClicks sauthi vadhu (top 8, fakt positive)
Pages gaining impressionsimpr − prevImpr sauthi vadhu
Pages that droppedclicks − prevClicks < 0 (client report ma optional)
New keywordsprevImpr = 0 ane impr ≥ 5
Position moversprevPos − pos sauthi vadhu (positive = improve)
Striking distanceposition 8–20 ane impr ≥ 20, non-branded
Low CTRimpr ≥ 100–300 ane CTR < 1%
Brandedquery ma brand term regex match (/Client A|sky line/i)
Non-brandedbaki badha, impressions thi sort
Keyword band≤3 Top 3 · ≤10 Page 1 · ≤20 Page 2 · >20 Beyond

11.5.I 8. Step 7 — Content sections (rewrites, ideas, fixes)

8.1 Page rewrites for this week (3 pages)

Kai page pasand karvi:

  1. High impressions + CTR < 1% + position 4–20 → FULL PAGE REWRITE
  2. Impressions vadhya pan position ghati (Google navi queries test kare chhe) → SEO-FOCUSED REWRITE
  3. Topic ni queries position 30+ par (topic own nathi kartu) → SEO-FOCUSED REWRITE + collection ↔︎ blog link

Darek rewrite ma:

  • Why (data): impressions, clicks, CTR, position, top queries numbers sathe
  • Full rewrite: Title (≤60), Meta (≤155), H1, akhi body (H2/H3 outline + text), FAQ (4 q), internal links, schema
  • SEO-focused rewrite: fakt badlav — title/meta, intro ma exact query, nava H2 (missing queries mathi), tables, FAQ, internal links

Example (Client A): /collections/porcelain-sinks — 3,471 impr, 17 clicks (0.5% CTR), pos 10.1; meta ma fakt bathroom, pan "porcelain kitchen sink" queries aave chhe → full rewrite.

8.2 New blog topics & collection ideas (90-day data)

Blog topic mate signal:

  • Question type query, position 1–10, pan dedicated page nathi (e.g. "why diamond segments wear too fast…" pos 3.7)
  • Navi query je jaldi vadhti hoy (15 → 157 impr)
  • Product/collection position 20+ — support blog thi help mle

Collection idea mate signal:

  • Ek j intent ni ghani queries (kitchen porcelain sink, white porcelain kitchen sink…) ane emne match karti collection nathi
  • Brand/product family queries (tenax proseal 767 impr) — dedicated collection nathi

Darek idea sathe: title, target keyword, supporting keywords, reason with numbers, slug, outline / products.

8.3 Fixes spotted on the site

Table format: Priority | Page | Problem | Reason | Fix / rewrite (exact navo title/meta/alt/H1 lakho, fakt "fix karo" nahi).


11.5.J 9. Step 8 — Report structure (website sections, upar thi niche)

  1. Hero — client, date range vs comparison, 7/28/90 buttons, Download PDF
  2. Overview — Clicks, Impressions, CTR, Avg position (prev + % change) + trend chart
  3. GSC: Blog posts — KPI + table (clicks, prev, Δ, impr, prev, Δ, CTR, pos)
  4. GSC: Other pages — same table
  5. What changed — 6 cards (gainers, impr gainers, new keywords, movers, striking, low CTR)
  6. Keyword positions — 2 tabs: Non-branded / Branded, "Search ↗" Google link (&gl=us&hl=en)
  7. GA4 — Organic sessions, users, engagement, orders, revenue; blog ane other landing pages alag
  8. Page rewrites (full
  • SEO-focused)
  1. New blog topics & collection ideas
  2. Fixes spotted on the site
  3. Footer — source + exact date ranges

Client type pramane badlo: Lead-gen → revenue ni jagyae form submits/calls · Local → city keywords · Blog site → GA4 revenue kadhi nakho.


11.5.K 10. Step 9 — Build

10.1 Live website (Next.js + Composio + ChatGPT)

Folder structure:

seo-report/ ├─ app/ │  ├─ page.js            ← UI (tabs, tables, buttons) │  ├─ layout.js          ← noindex meta │  ├─ globals.css        ← brand colour, dark mode, print CSS │  └─ api/ │     ├─ report/route.js ← GSC + GA4 fetch via Composio (?days=7|28|90) │     └─ ai/route.js     ← rewrites / ideas / fixes via ChatGPT + live page audit ├─ lib/ │  ├─ composio.js        ← Composio execute + date ranges │  └─ analyze.js         ← blog/other split, branded, what-changed rules ├─ .env.example ├─ package.json └─ README.md

Composio API call:

POST https://backend.composio.dev/api/v3/tools/execute/\<TOOL_SLUG> Header: x-api-key: <COMPOSIO_API_KEY> Body: { "connected_account_id": "<id>", "arguments": { ... } }

Environment variables (Vercel ma):

VariableShu nakhvu
COMPOSIO_API_KEYComposio → Settings → API key
COMPOSIO_USER_IDComposio user id (default default)
COMPOSIO_GSC_ACCOUNT_IDClient vala GSC connection ni ID
COMPOSIO_GA4_ACCOUNT_IDClient vala GA4 connection ni ID
COMPOSIO_GSC_TOOLGOOGLE_SEARCH_CONSOLE_SEARCH_ANALYTICS_QUERY
COMPOSIO_GA4_TOOLGOOGLE_ANALYTICS_RUN_REPORT
SITE_NAME / SITE_URLClient naam / URL
GSC_PROPERTYhttps://client.com/ athva sc-domain:client.com
GA4_PROPERTY_IDFakt number (e.g. 558018808)
BRAND_TERMScomma separated
OPENAI_API_KEY / OPENAI_MODELChatGPT key / gpt-4o-mini

ChatGPT system prompt (ai route):

You are a senior ecommerce SEO strategist and copywriter. Use ONLY the given data; never invent numbers. Output clean markdown in English.

Navo client = code change nahi. Fakt env vars badlo → Redeploy.

10.2 Snapshot artifact / HTML (aaj na data thi)

  1. Step 3–5 no data data.json ma save karo.
  2. HTML template ma const DATA=__DATA__; rakho, python thi replace karo:

python3 -c "t=open('tpl.html').read();d=open('data.json').read();open('report.html','w').write(t.replace('__DATA__',d))"

  1. JS syntax check: node -e "new Function(<script part>)".
  2. Artifact tarike publish karo ke ZIP ma index.html tarike mukho.

11.5.L 11. Step 10 — QA checklist (publish pehla)

  • Darek number source sathe match (GSC/GA4 ma 3–4 random numbers cross-check)
  • Koi demo/dummy data nathi (ke chhe to clearly label)
  • Period labels badha sections ma saacha
  • Duplicate (#anchor) URLs dedupe thai gaya
  • Branded keywords non-branded tab ma nathi
  • GA4 revenue 0 hoy to clearly lakhyu chhe
  • Darek rewrite/idea/fix ma "why" + number chhe
  • Mobile width (≈375px) par horizontal scroll nathi
  • noindex, nofollow meta chhe
  • Links client ni site par saacha khule chhe
  • Dark mode ma text vanchay chhe

11.5.M 12. Step 11 — Deploy (GitHub → Vercel)

  1. GitHub → New private repo (e.g. client-seo-report).
  2. ZIP extract karo → files upload karo (ZIP nahi). node_modules ane .next na mukvana.
  3. Vercel → Continue with GitHub → Add New Project → repo Import.
  4. Framework: Next.js (auto) → Environment Variables ma section 10.1 ni badhi values.
  5. Deploy → *.vercel.app link client ne mokalo.
  6. Pachhi koi badlav: GitHub ma file update → Vercel automatic redeploy.

Note: repo private chhe pan live link jene male e joi shake. noindex thi Google ma nahi aave. Client data chhe etle REPORT_PASSWORD (ke Vercel password protection) jaruri add karo.


11.5.N 13. Common problems & solutions (Client A mathi shikhyu)

ProblemKaranSolution
Composio ma client ni site nathiBiju Google account connectedClient access vala account thi navu connection (COMPOSIO_MANAGE_CONNECTIONS → add)
GA4 revenue $0Shopify purchase events GA4 ma nathi aavtaFix list ma High; Shopify "Google & YouTube" app thi GA4 link
Server mathi site fetch 403Proxy/allowlist blockBrowser ma site kholi same-origin fetch()
JS output cut thayTool output limit ~1000 charsData
 ma lakhi get_page_text thi vancho
window function navigation pachhi jato rahePage reloadFunction string localStorage ma rakho, eval thi chalavo
Ek j URL ghani var#elementor-toc… ke #anchor URLssplit('#')[0] + dedupe
"Copy URL to clipboard…" text URL maGSC row button text.replace(...) thi kadhi nakho
Totals "65K"GSC UI roundingRounded batavo ke API thi exact lo
Demo data thi client confusePreview ma fake numbersHamesha saacha data thi j final banavo

11.5.O 14. Navo report — ready prompt (copy-paste)

Act as Senior SEO Analyst + Dashboard Developer. Client: <NAME> | Site: <URL> | GSC property: <PROPERTY> | GA4 property: <ID> Platform: <Shopify/WordPress> | Market: <USA/UK/IN> | Brand terms: <a,b,c>

Follow my "SEO Live Report SOP": 1. GSC data 7/28/90 days (pages + queries, with comparison) — Composio ke Chrome. 2. GA4 Organic Search landing pages: sessions, users, orders, revenue. 3. Live audit of top 10 pages (title, meta, H1, alt, schema). 4. Sections: Overview, Blog traffic, Other pages, What changed, Keywords (Branded/Non-branded), GA4 blog + other landing revenue, Page rewrites (full + SEO-focused), New blog & collection ideas (90d, with reasons), Fixes spotted (priority + reason + exact fix). 5. Never invent numbers. Label every period. 6. Output: artifact (snapshot) + Next.js ZIP for GitHub/Vercel. Chat with me in Gujlish; report content in English.


11.5.P 15. Monthly routine (live website hoy to)

KyareShu karvuTime
Darek Monday7-day view kholo → What changed + Striking distance note karo10 min
Darek week"Generate page rewrites" → 1–3 pages update karo1–2 kalak
Mahina ni shuruat28-day + 90-day view → Ideas generate → 2–4 nava blogs/collections plan30 min
Mahina ma ek var"Scan pages & generate fixes" → High priority pehla fix1 kalak
Client meetingLink share + Overview, What changed, Rewrites done batavo—