Map the links.
Keep the evidence.

Start in the private workspace

• Open the companion plugin from your WordPress administrator account
• Use the site filter to focus on one managed website
• Training screen: all records and statuses are synthetic

Welcome to SiteMap Inflow. This guided walkthrough shows the actual private WordPress workspace, not a generic slide deck. Sign in to your own WordPress administrator account, then open site backlinks mapping. The companion plugin is separate from this public homepage. Use the site filter to focus on one website at a time. Every account name, status, publisher record, and link shown in this video is synthetic training data from an isolated local test site. Nothing here proves ownership, publication, outreach, or a live backlink. In your own workspace, start with a website you control and verify it before creating campaigns.

Add a website and prove ownership

• My websites → Add a website → exact hostname and profile
• New entries begin UNVERIFIED; registration is not ownership proof
• Publish the current TXT challenge in that domain’s authoritative DNS

Open My websites and choose Add a website. Enter a recognizable name, the exact hostname without a scheme, and a short profile that will help you organize research. Registering a site only creates a workspace record. It starts unverified and does not prove that you own the domain. In a real account, expand the DNS challenge and ownership check, add the current token as a TXT record at the displayed host in that domain’s authoritative DNS zone, wait for publication, then return and check it. This screenshot’s token is deliberately replaced with a redaction, and the sample status is not a DNS result. Never copy a token from a video or another website.

Plan a focused campaign

• Choose the verified website you own
• Use an exact HTTPS destination on that hostname
• Describe the campaign’s editorial purpose

Once your real website shows VERIFIED after a successful DNS check, open Campaigns and add a focused campaign. Select that website, choose an exact HTTPS destination on its registered hostname, and describe the editorial topic you intend to support. The campaign organizes your work; it does not find publishers, publish content, or obtain links. In this training interface, the website’s ownership state is a synthetic fixture so we can show the gated form. Do not treat it as verified ownership. Your live workspace must pass its own DNS challenge before the platform accepts a campaign destination.

Review publisher opportunities carefully

• Record an HTTPS source, specific relevance, and source evidence
• New prospects remain UNREVIEWED until a person checks them
• Only qualify after reviewing the live publisher page

Opportunity review is a manual research record, not an automatic prospecting engine. Add an HTTPS source page from a publisher allowed by your policy, connect the campaign if useful, and write specific topical relevance and source evidence. New prospects stay UNREVIEWED. In a real workflow, visit the live source yourself, check its content and editorial rules, confirm the factual context, and only then record a human review decision. Wikipedia and its subdomains are allowlisted by default here, but that is not an endorsement or a promise of placement. Other publishers need exact administrator approval. Every prospect in this video is fictional training data; no publisher page was reviewed or changed.

Prepare outreach for a human

• Draft only for a qualified, evidence-backed prospect
• Review and approve for manual use
• Approval never sends email or grants publisher consent

When a real prospect has been reviewed and qualified, you can prepare a manually written outreach draft tied to its campaign and prospect record. Keep the message accurate, relevant, respectful, and consistent with the publisher’s submission policy. The status moves to awaiting approval so an administrator can review the wording. Approval means only that the draft is ready for manual use. This platform does not send email, discover contacts, or ask a publisher to add a link. The simulated approval shown here is for screen demonstration only; it is not publisher consent, a sent message, or evidence that anyone replied.

Record and check an acquired backlink

• Add the real HTTPS source and exact owned destination
• Saving starts UNVERIFIED; only check after a link is actually published
• Review timestamps, HTTP evidence, anchor, rel, and retained history

A campaign does not create a backlink. After a publisher has independently chosen to publish a real link, add its actual HTTPS source page and the exact destination on your verified website in Backlink monitor. Saving the record starts it as UNVERIFIED. Run Check HTTPS backlink now only for a genuine source you are authorized to inspect. The checker reads the public page and destination, then stores a timestamped observation, including the anchor and rel value when available. The ACTIVE status and HTTP history in this training screen are synthetic fixtures: no DNS lookup, source request, destination request, or link placement took place. In real use, trust only the result of your own live check.

Stay in control of the evidence

• Use Publisher policy for exact host approvals
• Export saved records and review Operations
• Earned links depend on relevant content and publisher choice

Finish by checking Publisher policy, Reports and export, and Operations. Publisher approval is exact-host policy, not a quality guarantee. Exports contain saved records, not independent proof. This release does not automatically discover opportunities, create or place backlinks, send outreach, provide SEO metrics, or guarantee search rankings or AI citations. A backlink can only be earned when your content is genuinely useful and a publisher independently decides to reference it under their rules. Keep your evidence current, verify every site you control, and treat every status as an observation with a timestamp. The dashboard helps you organize careful work; people make the editorial decisions.