Expand SEO and AEO pages from verified Search Console demand

[lightcloud00]

Outcome

Grow useful organic discovery by answering real parking questions found in Google Search Console and Bing Webmaster Tools while keeping every page accurate and product-connected.

Dependencies

• Final domain and public website in Acquire final domain and replace candidate canonical/support URLs #10 and Deploy website and verify HTTPS, redirects, sitemap, and indexing setup #11
• Shared engine/provider lane in Register ParkNudge in the shared Google/Bing Engine and prove search launch #25
• Comparable Google/Bing baseline in Establish the privacy-preserving launch revenue scorecard #14

Plan

• Export non-brand queries and landing pages with provider, property/site identity, impressions, clicks, CTR or click rate, average position, country where available, and date range.
• Keep provider metrics separate when definitions differ and treat missing provider evidence as unknown.
• Improve high-impression/low-click titles and descriptions only when the page already answers the intent.
• Create a new page only when a coherent query cluster has a distinct user task and ParkNudge can provide a useful answer.
• Include a direct visible answer, practical steps, accurate product capability, internal links, and matching structured data where eligible.
• Validate accessibility, mobile layout, local links, sitemap, canonical, social metadata, and public-edge readback.
• Compare matched 28-day periods while accounting for low volume, provider lag, and seasonality.

Guardrails

• No mass-generated doorway pages, invented FAQs, location-page spam, scraped competitor copy, or unverified ticket-prevention claims.
• Structured data must match visible content.
• Google/Bing data unavailable is unknown, not zero.
• A sitemap or IndexNow receipt is not indexing, ranking, traffic, installs, or revenue.

Acceptance

• Every changed/new page links a query cluster, provider evidence, and date window.
• Static checks and responsive browser QA pass.
• Public URL readback and post-change provider metrics are attached.
• The experiment closes with continue, revise, or stop and updates the governed project record.

---

Scope / non-scope

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

Evidence and closure

Close only from exact current-source evidence plus the applicable independent readback. Keep local, GitHub/CI, provider, deployment, device, store, commerce, indexing, traffic, and revenue evidence distinct; one does not imply another.

Owner / lane

The repository delivery lane owns ordinary implementation and verification. The operator owns only actions explicitly marked as operator-only or protected.

Resolution plan

• Verified: 2026-08-25T05:34:24Z against main@04a6cd5e808720983471ee9595fd40bc94e1f0fe (commit time 2026-08-25T00:53:29Z).
• Source basis: Original issue body, all 4 comment(s), current default-branch tree, disposition-appropriate source-path checks, and referenced pull-request states.
• Disposition: Operator or external gate - execute only the bounded proof steps and stop at protected actions.
• Outcome: Grow useful organic discovery by answering real parking questions found in Google Search Console and Bing Webmaster Tools while keeping every page accurate and product-connected.

Current evidence and corrected premise

Source merge closeout

The approved StoreKit-copy source delta is complete. PR #27 merged exact verified head 5de334c as merge commit 9adadc6, and remote main reads back that merge SHA. The full exact-head verifier passed in 382.013 seconds; receipt state is success and log SHA-256 is 56737bceb54c3ce383a57c05a974f96e5597aa14c41c42db545a8b93b7f17039. This closes only the source merge lane; the independent growth and App Store gates in this issue remain tracked separately.
All 4 issue comment(s) were read. The newest is by @lightcloud00 at 2026-08-22T16:13:48Z.
Newest comment excerpt: ## Source merge closeout The approved StoreKit-copy source delta is complete. PR #27 merged exact verified head 5de334c as merge commit 9adadc6, and remote main reads back that merge SHA. The full exact-head verifier passed in 382.013 seconds; receipt state is success and log SHA-256 is 56737bceb54c3ce383a57c05a974f96e5597aa14c41c42db545a8b93b7f17039. This closes only the source merge lane; the independent growth and App Store gates in this issue remain tracked separately.
Verified source paths on this head:

• scripts/verify.sh
  Referenced pull requests checked:
• PR Use compliant Lifetime Pro copy #27: MERGED at 2026-08-22T16:03:26Z as 9adadc6

Resolution steps

1. Refresh the authoritative external state and bind it to the exact account, app, build, deployment, or provider identity.
2. Reconcile that readback with the issue-authored work below and identify the smallest remaining action.
3. Prepare the protected action, rollback, and failure receipt without exposing credentials or inferring authority.
4. Stop for the required operator decision or action, then execute it once through the owning workflow.
5. Validate the official readback and map it to every acceptance item before closure.

Grounded issue-authored detail

Scope / non-scope

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

Tests and acceptance

Acceptance

• Every changed/new page links a query cluster, provider evidence, and date window.
• Static checks and responsive browser QA pass.
• Public URL readback and post-change provider metrics are attached.
• The experiment closes with continue, revise, or stop and updates the governed project record.

---

Dependencies and stop gates

Dependencies

• Final domain and public website in Acquire final domain and replace candidate canonical/support URLs #10 and Deploy website and verify HTTPS, redirects, sitemap, and indexing setup #11
• Shared engine/provider lane in Register ParkNudge in the shared Google/Bing Engine and prove search launch #25
• Comparable Google/Bing baseline in Establish the privacy-preserving launch revenue scorecard #14
• Do not close this issue until every acceptance item is mapped to exact merged-head evidence.

Next AI first action

Review the top-10 shortlist, complete keep_current name disposition, and define one owned successful parked-car return to paid-conversion metric in issue #23.

[lightcloud00]

2026-08-20 US search-intelligence evidence

Goal: Review and sequence the evidence-backed ASO, SEO, AEO, competitor, and public-name opportunities for ParkNudge.

• Registry key/status: parknudge / active
• Canonical repository: lightcloud00/parknudge
• ASC identity/status: not_in_asc / not_in_asc
• Evidence batch: /Users/gus/Desktop/seo/portfolio-aso-submission-control/research/batches/20260820T104623Z-us
• ASC evidence SHA-256: 94a0ae6664e5a13e1832ad887397e82cf883aca3eed619efd6686b58ee353abb
• Keyword evidence SHA-256: 3a27f0cee67743912a509d472a5f2aa1f7d8a4afa60bf071d5834717672275da
• Name scorecards SHA-256: 03f7fee07d347a6e214b258e1d0bd3e30f13165939b3b8e975baa633fcc32f8f
• Canonical app note: AOS-Memory/02_projects/ParkNudge/CURRENT.md (open in Obsidian)
• Portfolio state: AOS-Memory/02_projects/portfolio-aso/2026-08-20-asc-search-intelligence.md (open in Obsidian)

Top 10 opportunities

Rank	Query	Score	Independent signals	Promoted
1	find my car app	81.22	2	yes
2	save parking location	80.41	4	yes
3	parking spot reminder	79.3	5	yes
4	parked car finder	68.3	2	yes
5	parking meter reminder	68.3	2	yes
6	how to find my car app	66.82	0	no
7	find my car app app	66.32	0	no
8	parking timer	66.2	2	yes
9	car location app	61.8	1	no
10	parking history	59.7	1	no

Name evidence

• Current: ParkNudge
• Evidence winner: ParkNudge: Parking Reminder (delta 13.0)
• Verdict: keep_current
• Reason: No candidate clears every rename gate; preserve the current or working identity and treat alternatives as research-only.
• Legal/trademark clearance: not_performed and remains a separate gate.

Acceptance checks

• Review the top 10 and retain only terms that match current product truth.
• Import the hashed batch through the canonical Search Intelligence Engine contracts when ready.
• Keep a promoted term only while two independent demand signals remain fresh.
• Treat unavailable GSC, GA4, Bing, ASC analytics, SerpAPI, or TinyFish evidence as unavailable—not zero.
• Reconcile the ASC identity before metadata planning.
• Obtain separate product-owner and legal approval before any public-name change.

Engine dependencies

lightcloud00/search-intelligence-engine#2, lightcloud00/search-intelligence-engine#3, lightcloud00/search-intelligence-engine#4, lightcloud00/search-intelligence-engine#8, lightcloud00/search-intelligence-engine#10, lightcloud00/search-intelligence-engine#13, lightcloud00/search-intelligence-engine#14

These are read-only dependencies during the active cross-thread Search Intelligence/Search Growth coordination freeze; this batch performs no engine issue or repository write.

Non-goals / protected boundaries

No ASC save or rename; no upload, TestFlight, App Review, submission, or release action; no website edit/deploy or indexing request; no advertising or billing change; no relaunch/deletion/lifecycle decision.

Agent Reach used public App Store discovery through its Jina lane. SerpAPI used 42 calls after verifying a 219-query balance and preserving the 50-query reserve. TinyFish used 22 requests total (one failed canary plus 21 successful searches). No subscription, credit, or purchase was made.

[lightcloud00]

Implementation, revenue, and trend roadmap — 2026-08-20 handoff

Status: the evidence batch is complete; the product decisions and implementation below are not complete.

• Portfolio batch: 20260820T104623Z-us
• Roadmap version/content: 2026-08-20.1 / 030b066bb592234904d51d23a931fff5eee6c28af67196bc3d100d7175c159ee
• Roadmap artifact SHA-256: ecb50c260ed0eb443c00dfcf078d3d61fe707bbdcfaf2b5f09b2029148019096
• Execution wave: 3 — Pre-ASC demand and offer validation
• Canonical issue: lightcloud00/parknudge#23; this comment extends that issue and does not create a duplicate.
• Canonical app note: AOS-Memory/02_projects/ParkNudge/CURRENT.md (open in Obsidian)
• Portfolio state: AOS-Memory/02_projects/portfolio-aso/2026-08-20-asc-search-intelligence.md (open in Obsidian)

Completed baseline

• 30 deduplicated opportunities; top shortlist: find my car app, save parking location, parking spot reminder, parked car finder, parking meter reminder.
• Five public competitors and name verdict keep_current; evidence winner ParkNudge: Parking Reminder.
• ASC: not_in_asc / not_in_asc; owned Google evidence: unavailable.

What is not done

• R0 · evidence_decision — Accept or reject every top-10 query against current product truth and record the reason in the canonical issue.
  • Proof: Ten explicit accept/reject decisions; promoted terms retain at least two independent signals.
• R1 · identity_and_name — Keep ParkNudge as the working name and revisit only if new collision or demand evidence clears the same decision gates.
  • Proof: One owner name verdict plus collision/legal status; no public rename in this phase.
• R2 · owned_measurement — Map an authorized GSC property or keep owned Google evidence explicitly unavailable. Keep ASC acquisition and identity work out of scope until a separate launch decision exists. GA4 and Bing remain unavailable until authorized connectors and receipts exist.
  • Proof: Availability and freshness for GSC, GA4, Bing, and ASC acquisition are recorded as evidence or unavailable, never zero.
• R3 · experiment_specification — Write one review-first ASO/SEO/AEO experiment specification with hypothesis, surface, baseline, success metric, stop condition, and rollback.
  • Proof: Approved specification only; implementation or publication requires separate authorization.
• R4 · revenue_validation — Define the offer and conversion event from owned evidence; ASC identity, launch, and public pricing remain separate decisions.
  • Proof: Activation, paid conversion, retention, refund/cancel state, and recognized revenue are reported separately where applicable.
• R5 · trend_loop — Schedule monthly public-demand/competitor review, quarterly name/offer review, and event-driven ASC refresh while enforcing provider caps.
  • Proof: Each refresh records source receipt, freshness, proxy versus owned class, and changed/no-change decision.

Revenue path

• Commercial question: Can repeated successful parked-car return support a truthful paid offer without widening current product claims?
• Gate: Define the offer and conversion event from owned evidence; ASC identity, launch, and public pricing remain separate decisions.
• Metric contract: Discovery, activation, paid conversion, retention, and recognized revenue must remain separate measures.
• No traffic, download, configured-commerce, or test-purchase result may be reported as recognized revenue.

Trend plan

• Monthly: Google Suggest and public App Store demand/competitor delta, with provider usage receipt.
• Quarterly: Name collision, pricing/offer visibility, review themes, and cross-surface consistency.
• Event-driven: ASC identity/review/build or material product-truth change triggers a new GET-only double-read baseline.
• A promoted opportunity or rename recommendation still requires two independent demand signals; unavailable evidence remains unavailable, never zero.
• Provider work stops on authentication failure, quota uncertainty, or a request for new spending.

Resume here

Next executable action: Review the top-10 shortlist, complete keep_current name disposition, and define one owned successful parked-car return to paid-conversion metric in issue #23.

Wave exit gate: Owner-approved product/name decision, owned measurement plan, and evidence-backed offer hypothesis; ASC remains a separate decision.

Engine import remains a read-only dependency at search-intelligence-engine#14 during the active coordination freeze; this update does not mutate the engine or GDS hierarchy.

Protected boundaries

No ASC save or rename; no build upload, TestFlight/App Review action, submission, or release; no website edit/deploy or indexing request; no advertising or billing change; no relaunch, deletion, or lifecycle decision. Product implementation and public experiments require separate authorization and proof.

[lightcloud00]

ASC/source checkpoint — 2026-08-22

Exact source 5de334cc3bd60a44abbbf2a19452c5bc8427b0f6 / tree c7406e390c5bc7089cd7d914f9056e6c31771485 is on draft PR #27. The normal pre-push hook ran full scripts/verify.sh at this SHA and passed. ASC metadata read back exactly. Lifetime Pro reads back at $9.99 with en-US Unlock history, custom reminders, costs, and CSV.; parent remains MISSING_METADATA. Fresh validation: 33 blocking / 1 warning. Source-only privacy/support copy is prepared; live host remains unreachable. Location/notification privacy, Sandbox, screenshots/build, review/legal remain open. No merge/upload/submission/release. Umbrella: lightcloud00/claudecode-workspace#1316.

[lightcloud00]

Source merge closeout

The approved StoreKit-copy source delta is complete. PR #27 merged exact verified head 5de334c as merge commit 9adadc6, and remote main reads back that merge SHA. The full exact-head verifier passed in 382.013 seconds; receipt state is success and log SHA-256 is 56737bceb54c3ce383a57c05a974f96e5597aa14c41c42db545a8b93b7f17039. This closes only the source merge lane; the independent growth and App Store gates in this issue remain tracked separately.