Purpose
Execute off-page authority creation and discovery acceleration through controlled distribution, cloud asset publishing, and forced indexation.
Primary Function
Primary Function
Create, deploy, and surface authority signals (links, mentions, indexed URLs) that support ranking, discovery, and trust for target pages.
UI Entry Point
UI Entry Point
Left Sidebar → Authority → Authority Building
Subsections:
📰 PR Distribution
☁️ Cloud Stacks
🧷 Indexer
Inputs
Inputs
Common Inputs (shared across tools)
Project context (OTTO Project, optional GBP Project)
Target URL (page receiving authority)
Keywords (topical alignment)
Knowledge Graph data (business info, location, authorship)
Media assets (logo, images, optional video)
Social profile URLs
Core Actions
Core Actions
📰 PR Distribution
📰 PR Distribution
Action: Distribute press releases across selected media channels.
User actions:
Create press release
Populate Knowledge Graph fields
Select distribution category and tiers
Review credit summary
Publish to selected channels
Execution characteristics:
Multi-step workflow with approval points
Channel-based distribution
Optional content variation and indexing services
☁️ Cloud Stacks
☁️ Cloud Stacks
Action: Publish AI-generated articles across cloud-hosted platforms with backlinks.
User actions:
Create Cloud Stack
Attach project and target URL
Provide contextual business data
Select cloud platforms (up to 14)
Publish stack
Execution characteristics:
Fixed credit cost regardless of number of platforms
Distributed asset deployment
Embedded backlinks to target URL
🧷 Indexer
🧷 Indexer
Action: Submit URLs for accelerated indexation.
User actions:
Create indexing batch
Provide batch name
Submit URLs (one per line)
Execution characteristics:
Batch-based submission
Status tracking per batch
Used post-publication or post-link acquisition
State Changes
State Changes
PR Distribution
Draft → Ready → Published
Unpublished PRs expose “Publish content” action
Published PRs populate publish date and status
Cloud Stacks
Draft → Select Sites → Published
Published state shows “Published X of 14 Sites”
Indexer
Submitted → Processing → Indexed (partial or complete)
Outputs
Outputs
Backlinks to target URLs
Brand mentions across distributed assets
Indexed URLs discoverable by search engines
Authority signals supporting ranking and trust
Dependencies
Dependencies
Indexer is commonly used after:
PR Distribution
Cloud Stack publication
Knowledge Graph accuracy affects:
Content consistency
Entity alignment
Credit availability gates execution
Non-Goals
Non-Goals
Does not perform:
Outreach negotiation
Publisher relationship management
LLM answer optimization
Does not replace:
Digital PR campaigns
QUEST analysis
Template-based scaling
Notes & Tips
Notes & Tips
📝 Index newly published PR and Cloud Stack URLs to reduce discovery lag.
📝 Cloud Stacks should target specific URLs, not entire domains.
📝 Review credit summary before publishing PR Distribution to avoid unexpected spend.
💡 Authority Building tools are execution-focused and designed to be combined, not used in isolation.
This article defines the execution layer of Authority in Search Atlas. It describes how authority signals are created, deployed, and surfaced through controlled distribution, cloud-based publishing, and indexation workflows.
Each component in this layer is designed to operate independently while producing outputs that can be consumed by downstream systems, including indexing services, Digital PR, and LLM visibility workflows. No strategic interpretation or outreach logic is applied at this stage, only execution, state transitions, and measurable outputs.
For research, opportunity discovery, and AI visibility, refer to the dedicated QUEST documentation. For outreach orchestration and response management, see the Digital PR and Templates execution layers.
This separation ensures Authority remains modular, predictable, and scalable across different visibility and ranking use cases.