Adding Tool Recommendations to Technical Tutorials Without Turning Them Into Ads

Put a tool recommendation after the reader understands the diagnostic question. The tutorial should still teach the method if the reader never opens your referral link.

Use a concept, command, interpretation sequence

For a DMARC lesson, first explain that the policy lives at _dmarc under the domain. Then show the query:

dig +short TXT _dmarc.example.com

Explain that p=none requests no DMARC-specific enforcement, while quarantine and reject request stronger handling of failures. The record alone does not establish whether a specific message passes: that requires an aligned SPF or DKIM pass.

Introduce the optional interface

After the manual explanation, offer the Beacon free check as another way to inspect public authentication signals. Tell readers which result to compare with the command output. If results differ, check the exact queried domain, timing, and cached DNS before assuming one tool is broken.

Keep implementation advice bounded

• Use example domains clearly and tell readers what to replace.
• Distinguish read-only lookup commands from DNS changes.
• Do not publish a copy-and-paste enforcement policy as a universal fix.
• Show how to test a real sending path when the lesson claims to verify mail authentication.
• Keep referral disclosure with the recommendation.

Finish with a learning check

Ask the reader to explain why a published record is different from a passing message. If they can answer that, the tutorial has taught something beyond clicking a checker.

Use the course tools-page exercise for graded instruction and RFC 7489 for protocol detail.