# What Awesome.Digital does and how to use it

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.

## Choose your starting point

### I want to understand my own website.
1. Enter your URL in the free check and save the report by email.
2. Review the findings, then claim an eligible free account from the verified report.
3. Reply to the report to discuss ongoing access or help with the work. Paid plans are assigned and invoiced during the assisted launch.

### I need to choose my client’s next piece of work.
1. Open the assigned website record and review the audit and connected evidence.
2. Check existing pages before commissioning content. Agree on a target URL, brief, and completion check.
3. Review the draft or fix, use an approved publishing path, and verify the live change.

### I need to show a client what happened.
1. Select the record and a reporting period with comparable evidence.
2. Review results separately from readiness, and include the work actually shipped.
3. Approve the report revision before delivery and use the next decision to guide further work.

## Website workspace
Keep the business, its website, and its evidence together.

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.

Input: A website URL and business context, such as services, audience, locations, and the questions customers ask. Connect only sources you are authorized to use.

1. Open the website from Records and check its business profile in Settings.
2. Connect available sources such as Google Search Console and Google Analytics to add search and traffic evidence.
3. Use Overview to orient yourself, then open the relevant work or measurement view.

Output: 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.

Where: Records → choose a website → Overview / Settings

Availability: 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.

[See the agency workflow](https://www.awesome.digital/agencies/)

## Audits and action plans
Find the issue and the page it affects.

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.

Input: 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.

1. Start the free check without signup, or run an available audit on your record.
2. Read the finding alongside its affected page and supporting evidence. Check the date and scope before acting.
3. Open Action Plan, validate the recommended change, and agree who will do it.

Output: 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.

Where: Free check, then record → Overview / Action Plan / History

Availability: 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.

[Follow a real finding into an action](https://www.awesome.digital/ai-visibility-audit/#worked-example)

## Page and keyword research
Decide what to update before writing something new.

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.

Input: 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.

1. Sync the sitemap and inspect the pages that already cover the topic.
2. Review recommendations to create, differentiate, refresh, consolidate, prune, clean up, or interlink pages. Validate each against the page and its evidence.
3. Choose the target page for an optimization brief or answer blocks, such as a direct opening answer, FAQ, or definition. Keep the reason with the decision.

Output: 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.

Where: Operator workspace → Content → Intelligence / Topics

Availability: 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.

[Turn page research into an action plan](https://www.awesome.digital/action-plan/)

## Content and campaigns
Turn source material into work your team can review.

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.

Input: 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.

1. In Content Creator, start through an agent conversation or manual setup with an approved article, intent, audience, and target page.
2. Prepare a draft or revision through the supported production workflow, then review the claims and quality checks. Content certification is a review stage, not a guarantee of accuracy.
3. Available output choices include an article, LinkedIn or Facebook post, carousel, YouTube video, and vertical short. Select the formats you want to request. Review any assets available in the campaign before release.

Output: 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.

Where: Record → Campaigns → Content Creator where enabled; operator workspace → Content → Articles / Briefs

Availability: 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.

[See how approved work reaches a website](https://www.awesome.digital/product/#publishing)

## Publishing and handoffs
Review the destination as carefully as the draft.

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.

Input: Reviewed content, an authorized destination, and the intended file or page. Check the proposed change before approving publication.

1. Prepare the content and confirm which site and destination it belongs to.
2. Use the supported GitHub publishing flow and review the branch or pull request.
3. After the destination deploys, inspect the public URL and record what actually shipped. A prepared draft or successful handoff is not proof of a live page.

Output: 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.

Where: Connected GitHub publishing; operator-assisted destination setup

Availability: 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.

[Plan the change and its verification](https://www.awesome.digital/action-plan/)

## Bring your own agent
Use your agent with your website records.

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.

Input: An account with access to the website record, an appropriate personal token, and a supported agent client or command-line workflow.

1. Open Account, then Agent access, and choose the appropriate access level and token use.
2. Connect a supported client using the setup guide, then inspect the enabled tools before asking it to work on a record.
3. Review the proposed work and receipts. Complete any required human approval yourself, and revoke the token when it is no longer needed.

Output: Agent-assisted work tied to a website record, with revocable access and the same role and plan boundaries.

Where: Account > Agent access; record agent where enabled

Availability: 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.

[Compare agent access paths](https://www.awesome.digital/integrations/#agents)

## Connected data and history
Build a history you can return to.

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.

Input: Authorized Google properties, available source history, the pages or queries you want to follow, and the date of a change.

1. Connect the intended Search Console and Analytics properties and check the source dates.
2. Use available query and page evidence to investigate topics, trends, and the pages that deserve attention.
3. Compare equivalent periods after a release. Ask an operator for deeper page-day analysis or warehouse work when required.

Output: Dated evidence and comparable reporting windows, or a clear explanation of what cannot yet be measured.

Where: Record connections, Results and Reports; detailed source and warehouse tools with an operator

Availability: 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.

[Explore data, warehouse, and trend features](https://www.awesome.digital/features/#data-history)

## Search and AI results
See what was observed, where it came from, and when.

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.

Input: 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.

1. Inspect available search, traffic, and AI evidence for the selected record.
2. Read the source, observation date, and limits of the measurement. Check whether a missing value means no data or a measured zero.
3. Compare the same scope after the change and decide whether to continue, revise, or investigate further.

Output: 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.

Where: Record → Results / Visibility → Citations; connected source views for operators

Availability: 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.

[Understand readiness, citations, and results](https://www.awesome.digital/measurement/)

## Client reports
Explain the work and the next decision to a client.

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.

Input: The website record, reporting period, included template, connected evidence, and any supporting uploads or manual context.

1. Create or assemble a report using the available sources and an included template.
2. Review the draft, source dates, limitations, and work summary. Resolve unsupported claims before approving the revision.
3. Deliver the approved revision through the supported report workflow. Return to it when deciding the next month’s work.

Output: 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.

Where: Record → Reports

Availability: 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.

[See reporting for an agency portfolio](https://www.awesome.digital/agencies/)

## See an actual report
[Public sample report](https://app.awesome.digital/sample-report?source_domain=www.awesome.digital&source_campaign=organic-growth-scan) is a fixed August 14, 2026 snapshot of an owned property, not a live dashboard or client success claim.

## Start with one website
Run the free check: https://app.awesome.digital/scan?source_domain=www.awesome.digital&source_campaign=organic-growth-scan
Paid plans are assigned and invoiced during the assisted launch. There is no self-serve checkout.