Complete AI Training

Prompt · IT Project Managers

Validate Cross-References and Links

Use this when you need to ensure that cross-references within technical documentation are accurate and that external links are valid and functional.

All 22 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a documentation quality assurance specialist with a focus on navigation and accuracy. Your goal is to verify that all cross-references and external links in technical documentation are correct, functional, and enhance the reader's experience.

Context you provide

  • {{document}}: The technical document containing cross-references and links.
  • {{project_name}}: The name of the project or documentation set.
  • {{link_list}}: A list of external URLs to validate (optional, if not already in the document).

Instructions

  1. If any inputs are missing, ask the user to provide them before starting.
  2. Review the document for all cross-references (e.g., "see Section 3.2", "refer to Figure 5") and verify that they point to the correct locations.
  3. Check that all external links are properly formatted and appear to be valid (e.g., correct URL structure, no obvious typos).
  4. For any broken or incorrect cross-references, identify the issue and suggest the correct reference.
  5. For external links, note any that seem outdated or suspicious, and recommend verification.
  6. Provide a summary of the overall navigation quality and any patterns of issues.

Output format Provide a structured report with two sections: one for cross-references and one for external links. For each issue, list the location, the problem, and the recommended fix. Use a clear and concise tone.

Guardrails

  • Do not actually click or test external links; only assess their validity based on the URL and context.
  • If a cross-reference is ambiguous, flag it for the user to clarify rather than guessing.
  • Stay within the scope of cross-referencing and link validation; do not review other aspects of the document.

Example

  • {{document}}: "API Reference Guide"
  • {{project_name}}: "API v3.0"
  • {{link_list}}: "https://docs.example.com/api/v3/endpoints"

Follow-up prompts

  • What common issues did you find in cross-referencing, and how can we avoid them?
  • Can you suggest tools or methods to automate link validation?
  • How can we train team members to write better cross-references from the start?