Tiered link building: follow the actual links
Tier labels are only useful when they describe real link destinations. Publishing order and link direction are separate facts, and a campaign diagram should show both clearly.
Editorial draft · hidden from search until final domain and author review are configured.
Common industry usage
In common tiered link-building terminology, Tier 1 pages link directly to the target website. Tier 2 pages link to a Tier 1 page. This convention varies across vendors, so always inspect the actual pages and report destinations.
CloudStackly’s application-specific flow
The application uses a source article on AWS. Supporting Tier 1 pages link to that AWS article. Tier 2 pages link to their assigned Tier 1 parent. The target landing page is linked from the AWS article. Therefore the link path is Tier 2 → Tier 1 → AWS article → target landing page.
Publication order
The software requires the AWS source asset to publish before support pages are planned. Tier 1 pages publish after the source, and a Tier 2 page can publish only after its assigned Tier 1 parent is live. This sequencing is a dependency for deployment, not a definition of the link direction.
What a report should show
A useful report lists each published page, its platform, status, URL and the page it links to. It should distinguish a successful deploy from URL verification and should not imply indexation or ranking results that were not measured.
Quality and risk
Every page should provide context and value beyond a link placement. Duplicating thin content across hosts or building layers solely to influence rankings can be risky and may not help users. Review policies and measure outcomes separately.
Before starting
Confirm the client facts and target page, review the article and anchor, inspect the planned parent assignment and ensure the platform is available. After publication, open each live URL and compare its real links with the report.