What will I receive?
Intent-grouped keywords and a proposed page map with source metrics and unknowns explicit. Scope: 300 keyword phrases. You also receive a validation record and any unresolved questions.
How is this work completed?
A Codex-operated queue handles the agreed job. Integration access is confirmed before work; an app listing does not mean a production executor is already installed. The storefront collects the brief; AI-assisted operator work begins after the scope and inputs are confirmed.
Does this include live account changes?
No live source changes are included. The deliverable is files, drafts, analysis or tested workflow source. Deployment, sending and destructive changes require a separate agreement.
How do I provide access safely?
Start with authorized source files or request connection compatibility review. Where a provider account is needed, use its secure hosted connection form after the auth configuration is ready. API keys, passwords and tokens must never be sent in chat, briefs or uploads.
What does the extended package add?
The scope and record limit stay the same. The extended package adds a runbook and three worked examples so another operator can repeat the process.
Is there a guaranteed business result?
No. The commitment is the stated deliverable and checks. Provider access, customer decisions and external business results remain outside that commitment.
When does the delivery target begin?
After the source material, access compatibility and acceptance requirements are confirmed. Missing inputs must be resolved before work begins.
What source material is needed for Semrush?
Confirm 300 keyword phrases. Identify supplied files, authorized account resources or a public reference URL. Confirm the actual export fields and account version in the brief. The shared example uses neutral fixture columns, not a certified vendor export schema.
What does the worked example prove?
The keyword clustering and page ownership example shows a small, fictional input and a reviewable output. It demonstrates the stated checks, not a completed client engagement, the full package quantity or a live Semrush connection.
What is excluded from the result?
Live account changes outside an explicitly approved sandbox creation scope; Persistent hosting, recurring monitoring, autonomous sending and production activation. Account edits and recurring operations are not included in this export-based scope.
Does this include a Semrush subscription or publishing pages?
No. Supply the authorized keyword export and target market for the declared 300 phrases. The handoff is a proposed intent grouping and page map with unknown metrics preserved. Software subscriptions, publishing and ranking guarantees are excluded.
What do I need to supply before work can start?
Required inputs: What should this delivery help you do?; Source material and scope; Requirements and acceptance checks; How will source material be provided?; I am authorized to provide this material. Use the request form for those inputs. Never include passwords, API keys or access tokens; account access, when needed, must be authorized through a secure connection.
How do the packages differ?
Complete delivery: 300 keyword phrases; includes the stated artifacts and validation record.; $129, target about 2 days after payment and complete inputs, 1 included revision. Delivery and runbook: Same 300 keyword phrases; adds reproducible operating instructions and three worked examples.; $178, target about 3 days after payment and complete inputs, 2 included revisions. Check the package comparison for quantities and optional extras.