Inside the product
Awesome.Digital is a workspace for website audits, page and keyword research, content production, publishing, and client reporting. Each website has a record that keeps its findings, work, and results together. Start with a URL; connect more evidence and use the tools included in your plan as the work grows.
Looking for a specific tool? Search the feature catalog or browse connections and integrations, including Search Console, GA4, BigQuery, GitHub, and your own agents.
Check My Site Free →No signup to start the check. Ongoing access, production work, and connected sources depend on your plan and setup.
Business owner
Agency or operator
Reporting
01 / Website workspace
Choose a website record before you start work. A record is the shared context for that business: its profile, connected sources, audit history, content, and reports.
See the agency workflow →A website URL and business context, such as services, audience, locations, and the questions customers ask. Connect only sources you are authorized to use.
One place to return to for this website, with its audit history and available evidence. An agency can switch between assigned client records without treating every client as the same business.
Find it: Records → choose a website → Overview / Settings
Access and scope: Signed-in users work within their owned or assigned records. Sources require the appropriate account access; viewing a record does not grant permission to change it.
02 / Audits and action plans
Run a check, inspect the findings, and use the action plan to choose work. The audit looks at technical access, content structure, query coverage, and authority. AI observations remain a separate form of evidence.
Follow a real finding into an action →Your website URL for the free check. In an account, the selected website record and the scope of the audit you are allowed to run.
A report and a prioritized starting point for work: what needs attention, why it matters, and which change to investigate first. The check does not silently rewrite the site.
Find it: Free check, then record → Overview / Action Plan / History
Access and scope: The free check covers a technical preview and sampled AI answers when available under its cap. Account audits and deeper research depend on the plan and available sources.
03 / Page and keyword research
Content intelligence connects the site inventory to topics, queries, and opportunities. It helps an operator investigate weak pages, missing answers, and overlapping coverage rather than treating every keyword as a new article.
Turn page research into an action plan →The existing pages and sitemap, plus available search queries, page performance, and keyword research. A specific service or buyer question gives the review a useful focus.
A page-level content decision supported by evidence. Refresh and consolidation candidates still need review; the tool does not make a redirect safe just by suggesting it.
Find it: Operator workspace → Content → Intelligence / Topics
Access and scope: The full Content Engine is an operator workspace. Research and production support are scoped with your package; this is not a promise that every client sees every operator tab.
04 / Content and campaigns
Prepare a content brief, generate or revise written content, and review it against the business and its sources. Campaigns can organize written and media outputs around a shared brief instead of starting every asset from scratch.
See how approved work reaches a website →The selected topic or page, business context, source material, and brand guidance. For a campaign, add the brief, source content, and the outputs you need.
A campaign brief and requested formats, plus drafts or revisions from supported production work. The wider operator workflow can also prepare answer blocks, content briefs, schema, and machine-readable files for review.
Find it: Record → Campaigns → Content Creator where enabled; operator workspace → Content → Articles / Briefs
Access and scope: Output choices are not a promise that every format is rendered or published end to end for every account. Generation, Campaigns, rendering, and production volume depend on enabled features and package scope. Founding beta access is not a blanket inclusion of content production or earned placements.
05 / Publishing and handoffs
For a connected GitHub site, publishing can use a branch and pull request so the change can be reviewed before it reaches the live website. Other destinations follow their own supported handoff.
Plan the change and its verification →Reviewed content, an authorized destination, and the intended file or page. Check the proposed change before approving publication.
A reviewable site change or an explicit publishing handoff, followed by a public URL to verify. Keep the release date for the later results comparison.
Find it: Connected GitHub publishing; operator-assisted destination setup
Access and scope: GitHub publishing is live for authorized records and included features. WordPress publishing is coming soon. Publer distribution is an operator workflow, not a client self-serve publishing screen. Other CMS work may need a manual handoff.
06 / Bring your own agent
The in-app record agent and personal agent access give you different ways to work with the same business context. Personal tokens let supported API, CLI, or MCP workflows act within your existing permissions.
Compare agent access paths →An account with access to the website record, an appropriate personal token, and a supported agent client or command-line workflow.
Agent-assisted work tied to a website record, with revocable access and the same role and plan boundaries.
Find it: Account > Agent access; record agent where enabled
Access and scope: Personal agent tokens are live. Hosted MCP has a narrower tool set than the operator CLI. Its protocol is live, but client verification, Claude app sign-in, and directory approval remain unverified. Hosted GSC, GA4, and content-opportunity reads are not yet enabled.
07 / Connected data and history
Connect Search Console and GA4 to the website record. Collected audits, queries, pages, and observations let later work use evidence from more than the latest snapshot. Platform exports also support analysis in BigQuery.
Explore data, warehouse, and trend features →Authorized Google properties, available source history, the pages or queries you want to follow, and the date of a change.
Dated evidence and comparable reporting windows, or a clear explanation of what cannot yet be measured.
Find it: Record connections, Results and Reports; detailed source and warehouse tools with an operator
Access and scope: Coverage depends on successful collection, permissions, and source windows. Previously lost data cannot be recreated. BigQuery is a platform capability, not a promise of a one-click customer warehouse connector or unlimited retention.
08 / Search and AI results
Use Results and citation views to examine visibility alongside the website work. Connected search and analytics sources add query, page, and traffic evidence. A readiness score, a model check, and an imported citation observation answer different questions.
Understand readiness, citations, and results →Authorized data connections and available audit or citation observations. Choose a comparable date range, query or prompt set, and page scope for a before-and-after review.
Evidence for the next decision, including inconclusive results. Citation research can show which sources appear in observed answers; it cannot guarantee the next answer will mention the business.
Find it: Record → Results / Visibility → Citations; connected source views for operators
Access and scope: Citation checks and connected measurement depend on plan, permission, and source availability. Collection may have usage limits or require confirmation. Connecting a source does not create missing historical observations.
09 / Client reports
Reports bring available evidence into a reviewable account of readiness, search, traffic, AI visibility, work shipped, and the next decision. Connected local sources can add local context.
See reporting for an agency portfolio →The website record, reporting period, included template, connected evidence, and any supporting uploads or manual context.
A report available in the app, as a PDF, or through approved email delivery. The free scan report and an ongoing client report are different deliverables.
Find it: Record → Reports
Access and scope: Report templates and actions depend on plan and record permissions. Agency branding adds your name and logo to the header, PDF, and delivery email; it does not include custom themes or a custom sender domain.
An actual output
This public report shows the difference between readiness, search outcomes, and AI observations. Read its evidence notes and next action to see how a report supports a decision.
On an owned or assigned record, included features let you connect a source, run an audit, read the plan, inspect citations and results, work with reports, and use supported GitHub publishing. Your role and plan determine the available actions. The full Content Engine and some connected-source tools remain operator workspaces.
Compare plans and assisted services →An operator can help interpret page research, prepare production work, connect a publishing destination, or manage delivery. A Loop Sprint scopes one diagnosis, fix, and re-measurement; Managed Loop provides ongoing scoped work. Paid access is currently assigned and invoiced, with no self-serve checkout.
Use the report reply path to agree on scope. Content approval, destination access, and actual publication remain distinct steps.
Run the free check to get your first evidence. Then decide whether you need a page fix, content work, connected measurement, or help running the process.
Check My Site Free →