This list only shows service areas that already have real published state pages in the live site.
California, Texas
This page answers the questions clients usually ask before starting: how the workflow runs, how reporting works, what is included, and how clearly the work is documented week to week.
Reports go out on the same agreed weekday each week, so the client always knows when the update is coming.
The workflow includes a dated log of shipped actions, what changed, and what result or effect the change was meant to produce.
The process is built to be reviewable without calls: clearer status, easier handoff, and less operational noise.
1SEO Company handles the execution layer around websites that already exist: technical fixes, SEO cleanup, website support, reporting, and local-market expansion.
The goal is to reduce website overhead for the business owner and turn the site into a measurable operating asset instead of a constant maintenance problem.
No. SEO is one part of the work, but the actual workflow is broader: fixing what is broken, improving the website structure, keeping the site maintained, supporting content updates, and connecting that work to reporting.
Usually no. The baseline offer is intentionally built around improving and supporting the website you already have.
If the right answer is a rebuild, a new page system, or a stronger development layer, that gets scoped directly instead of forcing unnecessary work into a generic package.
Yes. The current model assumes there is already a website, an existing operating reality, and often an owner or team that needs cleaner external execution support.
We do not require a blank slate. We work from the current condition of the site and the real constraints around it.
Reports are meant to be reviewed asynchronously and they are sent on the same agreed weekday each week. A good weekly update should show four things clearly: what shipped, what moved, what is blocked, and what happens next.
You can see the reporting format on the public results page and in the downloadable sample report.
Yes. The reporting rhythm is meant to stay predictable. Clients should not have to guess when updates are coming.
The exact weekday is agreed during onboarding, then kept stable so the reporting process becomes part of the operating routine instead of a surprise.
Yes. The workflow includes a dated action log that shows what was changed, when it was changed, and what result the action was meant to support.
That makes it easier to understand whether the team is actively working, what exactly shipped, and how the execution is moving week to week.
The site is intentionally built around an email-first workflow. That keeps the process calmer, more documented, and easier to review later.
Calls are not the default requirement for moving the work forward.
We use fixed monthly plans instead of hourly billing. That keeps scope clearer and makes it easier to connect price to execution depth.
The baseline structure has three retainers: Lite, Plus, and Premium. If none of them fit, we scope a custom plan.
No. The current public model is package-based. The point is to buy an execution layer, not to watch a timer.
The practical billing setup is confirmed during onboarding, but the public offer is a monthly retainer model.
If your business needs custom scoping or a different payment arrangement, that gets clarified before work starts.