# Awesome.Digital features

Browse named capabilities across the app and operator workflows. Availability depends on plan, record permissions, sources, and destination setup.

## AI visibility and competitor research
Inspect what a site makes clear and what AI systems actually say about it.

### AI readiness audit
Assess technical access, content structure, query coverage, and authority with evidence behind the findings.

Output: Readiness findings and a prioritized action plan.
Access: In app. Start with the free technical check. Account audit scope and usage depend on the plan.
[Explore the workflow](https://www.awesome.digital/ai-visibility-audit/)

### Sampled AI answers
See available sampled answers about a business alongside the free check.

Output: A small observed answer sample, separate from the readiness score.
Access: In app. Daily limits and provider availability apply. A sample is not continuous monitoring.
[Explore the workflow](https://www.awesome.digital/integrations/#ai-answer-services)

### Multi-model citation checks
Test selected buyer questions and inspect which brands and sources appear in the responses.

Output: Dated query/model observations with sources.
Access: In app. Paid feature and usage limits apply. Founding plans exclude Grok.
[Explore the workflow](https://www.awesome.digital/integrations/#ai-answer-services)

### AI mentions and share of voice
Inspect stored brand mentions and compare tracked-brand visibility within a defined query and model cohort.

Output: Separate mention evidence and frozen share-of-voice snapshots.
Access: In app. Requires eligible observations. Different sources and periods are not interchangeable; paid collection requires confirmation.
[Explore the workflow](https://www.awesome.digital/product/#results)

### Citation-winner research
Find the pages and publishers cited across observed AI answers, separating owned sources from competitors.

Output: A source corpus with recurrence and evidence limits for content and authority research.
Access: Operator-assisted. Research uses stored observations and supported collectors; it does not guarantee future citations.
[Explore the workflow](https://www.awesome.digital/product/#research)

### Exact-page competitor benchmarks
Compare the page ranking for a target query with the page you want to improve, rather than comparing whole domains alone.

Output: A page-level benchmark and an evidence-backed next test.
Access: Operator-assisted. Research depth and provider usage are scoped. A benchmark is not a ranking promise.
[Explore the workflow](https://www.awesome.digital/action-plan/)

### Query fan-out research
Explore related buyer questions and how they connect to the topic or service being investigated.

Output: A question set and coverage evidence for further research.
Access: Operator-assisted. Research and collection are separate from the free preview and from a guaranteed citation outcome.
[Explore the workflow](https://www.awesome.digital/product/#research)

## Crawling, technical SEO, and indexing
Inspect the actual pages and the files that help machines find and understand them.

### Rendered page crawling
Inspect rendered pages as well as sitemap inventory so research can include content that depends on JavaScript.

Output: Stored page evidence for audit and content analysis.
Access: Operator-assisted. Rendering is bounded by crawl scope and supported access; private pages are not automatically available.
[Explore the workflow](https://www.awesome.digital/product/#audit)

### PageSpeed and Core Web Vitals checks
Bring performance evidence into the technical review alongside access, links, metadata, and indexability.

Output: Performance findings tied to the checked URL and observation.
Access: In app. Available through audit and operator diagnostics; lab measurements and field data have different coverage.
[Explore the workflow](https://www.awesome.digital/fix-lanes/technical-foundation/)

### Business identity and entity checks
Check whether names, services, locations, profiles, and structured facts describe the same business.

Output: Identity gaps to verify and correct.
Access: In app. Results depend on supplied business context and available public evidence.
[Explore the workflow](https://www.awesome.digital/fix-lanes/trust-local-presence/)

### Indexing diagnosis
Investigate canonical targets, sitemap coverage, indexability, and available inspection evidence before requesting another page.

Output: A diagnosis linked to the affected URLs.
Access: Operator-assisted. Some indexing queue and request-priority workflows remain planned. Inspection does not compel indexing.
[Explore the workflow](https://www.awesome.digital/fix-lanes/technical-foundation/)

### IndexNow submission
Notify supporting search engines about eligible changed URLs after verifying the site-hosted key.

Output: A submission receipt to distinguish notification from actual indexing.
Access: Operator-assisted. Requires the matching key file on the website. Acceptance is not an indexing or ranking guarantee.
[Explore the workflow](https://www.awesome.digital/integrations/#indexnow)

## Content intelligence and existing-page improvement
Decide which pages to create, refresh, differentiate, consolidate, prune, or connect.

### Sitemap and content inventory
Sync the sitemap and review the pages the system has discovered and analyzed.

Output: A working page inventory with freshness and analysis context.
Access: Operator-assisted. Find it in the operator Content workspace. Validate excluded, noncanonical, and non-article resources before acting.
[Explore the workflow](https://www.awesome.digital/product/#research)

### Page, topic, and keyword mapping
Connect pages to the subjects and queries they cover, including observed topic clicks where the data supports them.

Output: A page-to-topic-to-query map for content decisions.
Access: Operator-assisted. Topic click windows and query history require connected evidence; they are not search-volume estimates.
[Explore the workflow](https://www.awesome.digital/integrations/#search-console)

### Content-gap analysis
Identify potentially unanswered questions and compare them with the pages that already exist.

Output: Create or improve candidates with supporting evidence.
Access: Operator-assisted. A suggested gap needs page and intent validation before a new page is commissioned.
[Explore the workflow](https://www.awesome.digital/ai-visibility-audit/#worked-example)

### Cannibalization and overlap detection
Spot pages that may overlap around a query or topic, then decide whether their purposes should be clarified.

Output: Differentiate or consolidation candidates for review.
Access: Operator-assisted. Overlap alone does not prove harmful search competition. Keep distinct buyer intents when they are useful.
[Explore the workflow](https://www.awesome.digital/product/#research)

### Content refresh recommendations
Find existing pages that may need stronger answers, fresher evidence, or clearer query alignment.

Output: A target URL, reason to update, and proposed next action.
Access: Operator-assisted. Review page evidence and recent changes before interpreting a weak signal as a failure.
[Explore the workflow](https://www.awesome.digital/action-plan/)

### Consolidation and pruning review
Evaluate whether overlapping or weak content should be combined, retained, redirected, or removed.

Output: A reviewable decision and canonical target where appropriate.
Access: Operator-assisted. Destructive changes and redirects require review. Suggestions do not automatically delete content.
[Explore the workflow](https://www.awesome.digital/action-plan/)

### Internal-link opportunities
Find useful connections between relevant pages while accounting for topic conflicts and overlap.

Output: Source-and-target link recommendations.
Access: Operator-assisted. Review the destination and anchor in context before publishing.
[Explore the workflow](https://www.awesome.digital/fix-lanes/content-authority/)

### Keyword quality and decision history
Keep the evidence and reasoning behind accepted or rejected keyword opportunities.

Output: A durable research trail instead of an unexplained keyword score.
Access: Operator-assisted. Research provenance and window matter; estimates are not observed site results.
[Explore the workflow](https://www.awesome.digital/product/#research)

## Writing, brand guidance, and technical assets
Produce page-specific drafts and assets from the business context and evidence.

### Brand and voice profiles
Provide brand guidance, writing preferences, and media styling so work can be prepared for the selected business.

Output: Reusable guidance for content and media production.
Access: Operator-assisted. Profiles must be configured and reviewed; an empty profile is not a completed brand setup.
[Explore the workflow](https://www.awesome.digital/product/#content)

### Page-specific optimization briefs
Select a page and prepare a brief around its purpose, audience, target question, and improvement needs.

Output: An actionable writing or optimization brief.
Access: Operator-assisted. Available in the operator Content workspace; validate recommendations against the live page.
[Explore the workflow](https://www.awesome.digital/product/#research)

### Direct answers, FAQs, and definitions
Prepare answer blocks for a selected page, including an opening answer, FAQ, or definition.

Output: Reusable answer text for editorial review.
Access: Operator-assisted. Generated answers need factual and contextual review before use.
[Explore the workflow](https://www.awesome.digital/product/#research)

### Article generation and revision
Generate or revise written content from a brief, source material, and brand context.

Output: A draft or revision ready for review.
Access: Operator-assisted. Content generation is plan-gated. The full Content Engine is an operator surface; access and production scope differ.
[Explore the workflow](https://www.awesome.digital/product/#content)

### Content review and certification
Review quality checks and source support before handing content to publishing.

Output: A review state and the issues that still need attention.
Access: Operator-assisted. Certification is not a guarantee that a claim is true. Human review remains necessary.
[Explore the workflow](https://www.awesome.digital/product/#content)

### Featured images and media assets
Prepare imagery for written or campaign content and keep it with the relevant work.

Output: Image assets for review and supported publishing paths.
Access: Operator-assisted. Generation and usage limits apply; featured-image usage can count toward article allowances.
[Explore the workflow](https://www.awesome.digital/product/#content)

### Structured data generation
Prepare JSON-LD schema from the selected business and page context.

Output: Schema markup to inspect and apply through an approved path.
Access: Operator-assisted. Generated markup must match visible facts; schema does not guarantee a rich result or citation.
[Explore the workflow](https://www.awesome.digital/fix-lanes/ai-discoverability/)

### llms.txt, robots.txt, and sitemap tools
Prepare and review machine-readable site files alongside the existing inventory.

Output: File content or a technical publishing handoff.
Access: Operator-assisted. Review crawler rules and canonical URLs before deployment. Word count is not the success test for these files.
[Explore the workflow](https://www.awesome.digital/fix-lanes/technical-foundation/)

## Campaigns, video, and repurposing
Turn approved source material into a coordinated set of outputs.

### Content Creator
Start with an agent conversation or manual setup using an approved article, intent, audience, and target page.

Output: A campaign brief and selected outputs to work on.
Access: In app. Campaigns requires the enabled campaign feature; it is not included on every plan.
[Explore the workflow](https://www.awesome.digital/product/#content)

### Articles, social posts, and carousels
Choose article, LinkedIn, Facebook, or carousel outputs within a campaign.

Output: Selected article, LinkedIn, Facebook, or carousel formats to prepare and review.
Access: In app. Visible format choices do not establish end-to-end generation or publication for every account.
[Explore the workflow](https://www.awesome.digital/product/#content)

### YouTube videos and vertical shorts
Choose 16:9 YouTube or 9:16 short-form output from approved source content; operator media tools also support square and longer-form work.

Output: Selected 16:9 YouTube or 9:16 short-form format. Supported operator production can prepare render artifacts.
Access: In app. Rendering, production scope, and destination support are separate from selecting a format.
[Explore the workflow](https://www.awesome.digital/product/#content)

### Narration and music beds
Operator media production can add voiced narration and a music bed that lowers under speech.

Output: Voiced, mixed media renders for review.
Access: Operator-assisted. Voice, brand, media rights, render gates, and production scope must be agreed.
[Explore the workflow](https://www.awesome.digital/integrations/#elevenlabs)

### Brand-film production
Create a designed brand film through the operator production workflow, with creative review and human approval.

Output: Approved film assets and destination-specific scheduling confirmations.
Access: Operator-assisted. An owned-brand film has been scheduled across five channels. This does not establish universal channel support for every content format.
[Explore the workflow](https://www.awesome.digital/integrations/#publer)

### Campaign review and release tracking
Keep output reviews, publishing intentions, and delivery receipts associated with the campaign.

Output: A visible distinction between prepared, approved, handed off, and verified work.
Access: In app. Campaign access and publishing support depend on enabled features and connected destinations.
[Explore the workflow](https://www.awesome.digital/product/#publishing)

## Publishing and distribution
Connect approved work to the destination, with a review and verification step.

### GitHub publishing and pull requests
Publish reviewed content through a connected repository, with branch and pull-request workflows.

Output: A reviewable change and publishing record.
Access: In app. Requires record permissions, a connected repository, and included features. Verify the deployed URL afterward.
[Explore the workflow](https://www.awesome.digital/integrations/#github)

### Astro content scheduling
Prepare future-dated content and inspect scheduled content in GitHub-backed Astro inventory.

Output: Scheduled content and its deployment handoff.
Access: Operator-assisted. The website needs the supported frontmatter and deploy schedule; a future date alone does not deploy a site.
[Explore the workflow](https://www.awesome.digital/integrations/#astro)

### Technical-file publishing
Prepare sitemap, robots, metadata, and AI-readable file changes for a supported publishing path.

Output: A bounded technical change to review and verify.
Access: Operator-assisted. Destination support and approval apply; crawler or indexing changes are not universal auto-fixes.
[Explore the workflow](https://www.awesome.digital/product/#publishing)

### Approved social scheduling
Hand approved media or social work to supported Publer operator workflows and reconcile the scheduling receipt. The general adapter is pilot-proven for LinkedIn, Facebook, and YouTube.

Output: Scheduled posts with readback evidence.
Access: Operator-assisted. Channel support varies by format and workflow. The provider composer/calendar remains in Publer.
[Explore the workflow](https://www.awesome.digital/integrations/#publer)

### WordPress publishing
The product has WordPress connection and content metadata work, while the publish action returns a coming-soon response.

Output: A planned WordPress publishing destination.
Access: Coming soon. Do not treat a connected WordPress account as a working live publish path.
[Explore the workflow](https://www.awesome.digital/integrations/#wordpress)

### Manual CMS handoffs
Prepare the reviewed content and destination instructions when a supported direct publish path is unavailable.

Output: A package an operator or site owner can publish and verify.
Access: Operator-assisted. A handoff is not proof that the website changed.
[Explore the workflow](https://www.awesome.digital/product/#publishing)

## Connected data, history, warehouse, and trends
Bring your evidence together and keep collected history available for later decisions.

### Search Console queries and pages
Connect Google Search Console to inspect clicks, impressions, positions, queries, pages, countries, devices, and trends.

Output: Search evidence tied to the website and date window.
Access: In app. Connection needs authorized property access. Detailed analysis views can be operator-assisted.
[Explore the workflow](https://www.awesome.digital/integrations/#search-console)

### Google Analytics traffic and events
Connect GA4 to bring traffic, pages, sources, events, and available conversion evidence into the review.

Output: Traffic and behavior context alongside search and audit findings.
Access: In app. Requires the correct property and permissions. Freshness and available collection history limit comparisons.
[Explore the workflow](https://www.awesome.digital/integrations/#google-analytics)

### Stored audit, query, and page history
Retain collected audits, observations, and search query/day and page/day facts so analysis can use a history rather than only the latest pull.

Output: Historical evidence to revisit across reporting periods.
Access: Operator-assisted. Coverage depends on successful collection and the source window. Data already lost upstream cannot be reconstructed; no unlimited-retention promise is implied.
[Explore the workflow](https://www.awesome.digital/integrations/#bigquery)

### BigQuery analytical warehouse
Export supported fact tables into BigQuery using incremental export watermarks.

Output: A warehouse copy of supported snapshots and analytical facts.
Access: Operator-assisted. BigQuery is part of the platform’s data operations. Historical coverage depends on successful collection and source windows. This is not a self-serve customer warehouse connector.
[Explore the workflow](https://www.awesome.digital/integrations/#bigquery)

### Trends and period comparisons
Review changes in available search, analytics, and report evidence over defined periods.

Output: Trend context with the source and observation window attached.
Access: In app. Some page trend reads depend on exact URL matching and available daily facts. An unavailable trend is not zero traffic.
[Explore the workflow](https://www.awesome.digital/product/#results)

### Before-and-after intervention analysis
Compare a shipped page change with comparable page-day facts and a recorded release date.

Output: A bounded impact comparison or an explicit reason it cannot be measured.
Access: Operator-assisted. Comparable cohorts and coverage are required. The command-line impact capability does not imply a complete self-serve attribution screen.
[Explore the workflow](https://www.awesome.digital/measurement/)

### Recurring source sync and freshness
Collect supported connected-source evidence on schedules and inspect source state, observation dates, and stale data.

Output: A record of available evidence and collection health.
Access: Operator-assisted. Schedules and source coverage vary. Paid SERP or AI collection needs explicit opt-in and budget scope.
[Explore the workflow](https://www.awesome.digital/integrations/)

### Evidence uploads
Bring CSV, PDF, and image evidence into reporting alongside connected data and manual context.

Output: Supporting material for a reviewed report.
Access: In app. Uploads require the right record access and interpretation; an uploaded figure is not automatically verified.
[Explore the workflow](https://www.awesome.digital/product/#reports)

## Local presence, reviews, and listings
Connect business locations and verify the public identity behind them.

### Google Business Profile evidence
Connect eligible business locations and include available profile and review evidence in the record.

Output: Local context and multi-location review provenance.
Access: In app. Requires authorized access and linked locations. Local report sections depend on the connection.
[Explore the workflow](https://www.awesome.digital/integrations/#google-business-profile)

### Name, address, and phone consistency
Compare business identity and contact information across available profile and listing evidence.

Output: Discrepancies to inspect and resolve.
Access: Operator-assisted. A detected mismatch requires verification; it is not an automatic directory edit.
[Explore the workflow](https://www.awesome.digital/fix-lanes/trust-local-presence/)

### Listing inventory, scores, and tiers
Review discovered listings, their kinds, verification states, and the priority of follow-up work.

Output: A listing worklist with evidence and status context.
Access: In app. Listing scores are diagnostics. Discovery is not proof of ownership, successful submission, or approval by a directory.
[Explore the workflow](https://www.awesome.digital/fix-lanes/trust-local-presence/)

## Earned authority and outreach
Research opportunities and track approved outreach with evidence at every step.

### Earned-authority research
Bring source research, prospects, campaign copy, and placement observations into one record-bound workflow.

Output: A reviewed authority opportunity and campaign evidence.
Access: Operator-assisted. Earned-placement features and service scope are separate from a free audit or general founding beta access.
[Explore the workflow](https://www.awesome.digital/integrations/#lemlist)

### Outreach preview and human approval
Review the campaign and intended provider action before sending through a supported connection.

Output: An approved campaign and provider receipt.
Access: Operator-assisted. A signed-in person must confirm and start lemlist sending. An agent can prepare or pause supported work, not perform that human confirmation.
[Explore the workflow](https://www.awesome.digital/integrations/#lemlist)

### Delivery, replies, and placement evidence
Reconcile provider delivery and reply events with prospects, suppression states, and reviewed placement observations.

Output: An evidence trail for what was sent, what happened, and what remains unverified.
Access: Operator-assisted. Provider bindings and exact event evidence are required. Sending does not guarantee a placement.
[Explore the workflow](https://www.awesome.digital/integrations/#highlevel)

## Agency workspaces and reporting
Keep clients separate while giving each one a clear account of the work.

### Assigned client records
Work across a portfolio while keeping business context, source connections, and permissions tied to the selected website.

Output: A separate workspace and history for each assigned record.
Access: In app. A plan does not grant access to another client’s record.
[Explore the workflow](https://www.awesome.digital/agencies/)

### Evidence-qualified report builder
Assemble or draft a report from available readiness, search, traffic, AI, local, and work-shipped evidence.

Output: A reviewable report with sources, dates, limitations, and the next decision.
Access: In app. Templates depend on plan and source availability. The free scan report is a different deliverable.
[Explore the workflow](https://www.awesome.digital/product/#reports)

### Report revisions and delivery approval
Keep a frozen report revision and approve it before supported email delivery.

Output: A versioned report available in app, PDF, or approved email delivery.
Access: In app. Owner/write permissions apply. A report draft cannot be treated as an approved send.
[Explore the workflow](https://www.awesome.digital/product/#reports)

### Monthly and weekly report templates
Use the included recurring report format to review a period of work and evidence.

Output: A repeatable reporting structure.
Access: In app. Monthly templates are available on included paid plans; the weekly template is an Agency feature. A template is not an unconditional automatic send.
[Explore the workflow](https://www.awesome.digital/pricing/)

### Agency report branding
Put the agency name and logo on the report header, PDF, and delivery email.

Output: A branded client deliverable.
Access: In app. Agency feature. Custom themes, colors, and sender domains are not included.
[Explore the workflow](https://www.awesome.digital/agencies/)

## Your agents, analytics operations, and connected tools
Use the record through supported agent access and operator tools as well as the app.

### Record-scoped AI agent
Work through an enabled agent conversation with the selected website or campaign as context.

Output: A conversation and supported tool work tied to the record.
Access: In app. Chat is plan-gated. Record permissions and confirmation boundaries still apply.
[Explore the workflow](https://www.awesome.digital/product/#agents)

### Bring your own agent
Create a personal agent token for supported API or command-line workflows, with access limited to your permissions and records.

Output: Revocable agent access and a record of token activity.
Access: In app. Set up under Account → Agent access. Agent usage shares applicable plan limits; credentials are not shared across clients.
[Explore the workflow](https://www.awesome.digital/integrations/#agent-access)

### Hosted MCP server
The hosted Awesome.Digital endpoint and personal MCP token protocol are live, with a documented Claude Code setup path.

Output: Access to the currently enabled tool set.
Access: Limited rollout. The server and token protocol are live. The client setup guide names Claude Code; client verification, Claude app sign-in, and directory approval remain unverified. GSC, GA4, and content-opportunity reads are not enabled on this hosted tool set yet.
[Explore the workflow](https://www.awesome.digital/integrations/#hosted-mcp)

### Operator CLI and evidence exports
Use record-scoped commands for supported audits, page research, reports, data reads, and publishing handoffs.

Output: Structured receipts, JSON or CSV evidence, and reviewable work packages.
Access: Operator-assisted. The operator CLI is broader than the hosted MCP catalog. Supported commands and permissions must be checked for the chosen workflow.
[Explore the workflow](https://www.awesome.digital/integrations/#agent-access)

### Google Tag Manager operations
Inspect containers, prepare or stage changes, and use supported version, publish, and verification steps.

Output: A reviewed tracking change and write receipt.
Access: Operator-assisted. Requires the correct container binding, Google scopes, and explicit approval for live writes.
[Explore the workflow](https://www.awesome.digital/integrations/#tag-manager)

### Google Ads operator controls
Read account performance and use supported broker-backed actions through the operator workflow.

Output: Account evidence or an explicitly approved advertising change.
Access: Operator-assisted. Ads account binding, scopes, and live-action confirmation apply. This is not unrestricted self-serve campaign management.
[Explore the workflow](https://www.awesome.digital/integrations/#google-ads)

### CRM, appointment, and form context
Read supported HighLevel contacts, conversations, campaign evidence, workflows, appointments, and form submissions for the bound record.

Output: Operational context and provider evidence alongside the website work.
Access: Operator-assisted. HighLevel API permissions and provider coverage apply. Reading workflows is not permission to enroll contacts or send messages.
[Explore the workflow](https://www.awesome.digital/integrations/#highlevel)

Start with the free check: https://app.awesome.digital/scan?source_domain=www.awesome.digital&source_campaign=organic-growth-scan