Explore Awesome.Digital features

Output: Readiness findings and a prioritized action plan.

Scope: Start with the free technical check. Account audit scope and usage depend on the plan.

Output: A small observed answer sample, separate from the readiness score.

Scope: Daily limits and provider availability apply. A sample is not continuous monitoring.

Output: Dated query/model observations with sources.

Scope: Paid feature and usage limits apply. Founding plans exclude Grok.

Output: Separate mention evidence and frozen share-of-voice snapshots.

Scope: Requires eligible observations. Different sources and periods are not interchangeable; paid collection requires confirmation.

Output: A source corpus with recurrence and evidence limits for content and authority research.

Scope: Research uses stored observations and supported collectors; it does not guarantee future citations.

Output: A page-level benchmark and an evidence-backed next test.

Scope: Research depth and provider usage are scoped. A benchmark is not a ranking promise.

Output: A question set and coverage evidence for further research.

Scope: Research and collection are separate from the free preview and from a guaranteed citation outcome.

Output: Stored page evidence for audit and content analysis.

Scope: Rendering is bounded by crawl scope and supported access; private pages are not automatically available.

Output: Performance findings tied to the checked URL and observation.

Scope: Available through audit and operator diagnostics; lab measurements and field data have different coverage.

Output: Identity gaps to verify and correct.

Scope: Results depend on supplied business context and available public evidence.

Output: A diagnosis linked to the affected URLs.

Scope: Some indexing queue and request-priority workflows remain planned. Inspection does not compel indexing.

Output: A submission receipt to distinguish notification from actual indexing.

Scope: Requires the matching key file on the website. Acceptance is not an indexing or ranking guarantee.

Output: A working page inventory with freshness and analysis context.

Scope: Find it in the operator Content workspace. Validate excluded, noncanonical, and non-article resources before acting.

Output: A page-to-topic-to-query map for content decisions.

Scope: Topic click windows and query history require connected evidence; they are not search-volume estimates.

Output: Create or improve candidates with supporting evidence.

Scope: A suggested gap needs page and intent validation before a new page is commissioned.

Output: Differentiate or consolidation candidates for review.

Scope: Overlap alone does not prove harmful search competition. Keep distinct buyer intents when they are useful.

Output: A target URL, reason to update, and proposed next action.

Scope: Review page evidence and recent changes before interpreting a weak signal as a failure.

Output: A reviewable decision and canonical target where appropriate.

Scope: Destructive changes and redirects require review. Suggestions do not automatically delete content.

Output: Source-and-target link recommendations.

Scope: Review the destination and anchor in context before publishing.

Output: A durable research trail instead of an unexplained keyword score.

Scope: Research provenance and window matter; estimates are not observed site results.

Output: Reusable guidance for content and media production.

Scope: Profiles must be configured and reviewed; an empty profile is not a completed brand setup.

Output: An actionable writing or optimization brief.

Scope: Available in the operator Content workspace; validate recommendations against the live page.

Output: Reusable answer text for editorial review.

Scope: Generated answers need factual and contextual review before use.

Output: A draft or revision ready for review.

Scope: Content generation is plan-gated. The full Content Engine is an operator surface; access and production scope differ.

Output: A review state and the issues that still need attention.

Scope: Certification is not a guarantee that a claim is true. Human review remains necessary.

Output: Image assets for review and supported publishing paths.

Scope: Generation and usage limits apply; featured-image usage can count toward article allowances.

Output: Schema markup to inspect and apply through an approved path.

Scope: Generated markup must match visible facts; schema does not guarantee a rich result or citation.

Output: File content or a technical publishing handoff.

Scope: Review crawler rules and canonical URLs before deployment. Word count is not the success test for these files.

Output: A campaign brief and selected outputs to work on.

Scope: Campaigns requires the enabled campaign feature; it is not included on every plan.

Output: Selected article, LinkedIn, Facebook, or carousel formats to prepare and review.

Scope: Visible format choices do not establish end-to-end generation or publication for every account.

Output: Selected 16:9 YouTube or 9:16 short-form format. Supported operator production can prepare render artifacts.

Scope: Rendering, production scope, and destination support are separate from selecting a format.

Output: Voiced, mixed media renders for review.

Scope: Voice, brand, media rights, render gates, and production scope must be agreed.

Output: Approved film assets and destination-specific scheduling confirmations.

Scope: An owned-brand film has been scheduled across five channels. This does not establish universal channel support for every content format.

Output: A visible distinction between prepared, approved, handed off, and verified work.

Scope: Campaign access and publishing support depend on enabled features and connected destinations.

Output: A reviewable change and publishing record.

Scope: Requires record permissions, a connected repository, and included features. Verify the deployed URL afterward.

Output: Scheduled content and its deployment handoff.

Scope: The website needs the supported frontmatter and deploy schedule; a future date alone does not deploy a site.

Output: A bounded technical change to review and verify.

Scope: Destination support and approval apply; crawler or indexing changes are not universal auto-fixes.

Output: Scheduled posts with readback evidence.

Scope: Channel support varies by format and workflow. The provider composer/calendar remains in Publer.

Output: A planned WordPress publishing destination.

Scope: Do not treat a connected WordPress account as a working live publish path.

Output: A package an operator or site owner can publish and verify.

Scope: A handoff is not proof that the website changed.

Output: Search evidence tied to the website and date window.

Scope: Connection needs authorized property access. Detailed analysis views can be operator-assisted.

Output: Traffic and behavior context alongside search and audit findings.

Scope: Requires the correct property and permissions. Freshness and available collection history limit comparisons.

Output: Historical evidence to revisit across reporting periods.

Scope: Coverage depends on successful collection and the source window. Data already lost upstream cannot be reconstructed; no unlimited-retention promise is implied.

Output: A warehouse copy of supported snapshots and analytical facts.

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

Output: Trend context with the source and observation window attached.

Scope: Some page trend reads depend on exact URL matching and available daily facts. An unavailable trend is not zero traffic.

Output: A bounded impact comparison or an explicit reason it cannot be measured.

Scope: Comparable cohorts and coverage are required. The command-line impact capability does not imply a complete self-serve attribution screen.

Output: A record of available evidence and collection health.

Scope: Schedules and source coverage vary. Paid SERP or AI collection needs explicit opt-in and budget scope.

Output: Supporting material for a reviewed report.

Scope: Uploads require the right record access and interpretation; an uploaded figure is not automatically verified.

Output: Local context and multi-location review provenance.

Scope: Requires authorized access and linked locations. Local report sections depend on the connection.

Output: Discrepancies to inspect and resolve.

Scope: A detected mismatch requires verification; it is not an automatic directory edit.

Output: A listing worklist with evidence and status context.

Scope: Listing scores are diagnostics. Discovery is not proof of ownership, successful submission, or approval by a directory.

Output: A reviewed authority opportunity and campaign evidence.

Scope: Earned-placement features and service scope are separate from a free audit or general founding beta access.

Output: An approved campaign and provider receipt.

Scope: A signed-in person must confirm and start lemlist sending. An agent can prepare or pause supported work, not perform that human confirmation.

Output: An evidence trail for what was sent, what happened, and what remains unverified.

Scope: Provider bindings and exact event evidence are required. Sending does not guarantee a placement.

Output: A separate workspace and history for each assigned record.

Scope: A plan does not grant access to another client’s record.

Output: A reviewable report with sources, dates, limitations, and the next decision.

Scope: Templates depend on plan and source availability. The free scan report is a different deliverable.

Output: A versioned report available in app, PDF, or approved email delivery.

Scope: Owner/write permissions apply. A report draft cannot be treated as an approved send.

Output: A repeatable reporting structure.

Scope: Monthly templates are available on included paid plans; the weekly template is an Agency feature. A template is not an unconditional automatic send.

Output: A branded client deliverable.

Scope: Agency feature. Custom themes, colors, and sender domains are not included.

Output: A conversation and supported tool work tied to the record.

Scope: Chat is plan-gated. Record permissions and confirmation boundaries still apply.

Output: Revocable agent access and a record of token activity.

Scope: Set up under Account → Agent access. Agent usage shares applicable plan limits; credentials are not shared across clients.

Output: Access to the currently enabled tool set.

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

Output: Structured receipts, JSON or CSV evidence, and reviewable work packages.

Scope: The operator CLI is broader than the hosted MCP catalog. Supported commands and permissions must be checked for the chosen workflow.

Output: A reviewed tracking change and write receipt.

Scope: Requires the correct container binding, Google scopes, and explicit approval for live writes.

Output: Account evidence or an explicitly approved advertising change.

Scope: Ads account binding, scopes, and live-action confirmation apply. This is not unrestricted self-serve campaign management.

Output: Operational context and provider evidence alongside the website work.

Scope: HighLevel API permissions and provider coverage apply. Reading workflows is not permission to enroll contacts or send messages.