Which URL should identify an individual answer in QAPage?

Definition: Use the url property of each Answer with a direct URL to that answer. In Google's QAPage example, the URL combines the question page with a fragment such as #acceptedAnswer or #suggestedAnswer1, and the HTML answer element has the matching id.

Key facts

• Google defines Answer.url as a URL that links directly to the answer and illustrates https://www.examplesite.com/question#answer1 in its QAPage structured data documentation.
• Google's example gives acceptedAnswer and suggestedAnswer objects answer-specific fragments in their URLs.
• RFC 3986 defines a fragment identifier as the URI component beginning with #; it can identify a secondary resource such as a portion or subset of the primary resource.
• The WHATWG HTML Standard says an element's id is its unique identifier and can link to a specific part of a document using fragments.

What belongs in Answer.url?

As of 8 September 2026, Google's QAPage documentation describes url as a URL that links directly to the answer. The property belongs on each Answer, whether the answer is held in acceptedAnswer or suggestedAnswer. The documented format keeps the question page path and adds a fragment naming the answer.

{
  "@type": "Answer",
  "text": "Answer text.",
  "url": "https://example.com/question#answer1"
}

The #answer1 part is the URL's fragment component. It identifies the answer within the question page, so the destination is the answer's location on that page.

How does the fragment reach the answer?

A fragment identifier is the part after #. RFC 3986 says it permits indirect identification of a secondary resource by reference to a primary resource and additional identifying information. The RFC also says that fragment semantics depend on the media type of the retrieved representation. For an HTML page, the WHATWG HTML Standard says the id attribute specifies an element's unique identifier and that the identifier can link to a specific part of a document using fragments.

<div id="acceptedAnswer" itemprop="acceptedAnswer"
     itemscope itemtype="https://schema.org/Answer">
  <div itemprop="text">Answer text.</div>
  <a itemprop="url"
     href="https://example.com/question#acceptedAnswer">Answer Link</a>
</div>

The fragment in href and the element's id use the same token. A direct answer link therefore needs a stable fragment value in the answer URL and a matching HTML target. RFC 3986 says fragment semantics are unknown when no representation defines them.

How are accepted and suggested answers addressed?

Google defines acceptedAnswer as a top answer accepted in some way on the site. It defines suggestedAnswer as one possible answer that has not been accepted as a top answer. Both are Answer values inside Question, and Google's JSON-LD example gives each answer object a url with its own fragment, including #acceptedAnswer, #suggestedAnswer1, and #suggestedAnswer2, in the QAPage documentation.

The fragment should identify the answer container represented by the corresponding Answer object. A page with several answers therefore exposes a separate target for each answer, including the accepted answer and each suggested answer shown in the markup.

What should be checked before publishing?

Google's documentation recommends validating structured data with the Rich Results Test. It also recommends deploying pages that contain the markup and using the URL Inspection tool to test how Google sees the page. The page should be accessible to Google and free of blocks from robots.txt, a noindex tag, or login requirements, according to the same QAPage documentation.

For the answer link itself, the check covers three matching values: the Answer.url fragment, the id on the answer element, and the fragment in any visible answer link. RFC 3986 states that a fragment is processed with the representation of the primary resource, so the HTML target belongs on the page returned by the URL.

Related terms

• QAPage structured data
• URL fragment identifiers
• Structured data
• Schema.org @id

FAQ

Should the answer URL be the page URL without a fragment?

Google's example uses a fragment in each answer URL, such as #acceptedAnswer. For an individual answer, the documented direct-link pattern includes the question page and the fragment that identifies the answer.

How should the fragment value relate to the HTML?

Use the same value in the answer's url after # and in the answer element's id. WHATWG calls id a unique identifier for an element, while RFC 3986 leaves fragment semantics to the representation's media type.

Does Google require a particular fragment name?

Google documents examples such as #answer1 and #suggestedAnswer1; its documentation does not state a single required naming pattern. The corresponding HTML id gives the fragment its target on the page.

Sources

1. Google Search Central, "Q&A (QAPage) structured data", 8 September 2026
2. RFC Editor, "Uniform Resource Identifier (URI): Generic Syntax", January 2005
3. WHATWG, "HTML Standard, The id attribute", 16 October 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer