comaps/website
11
24
Fork
You've already forked website
14

add json-ld faq schema #493

Merged
gedankenstuecke merged 2 commits from IXVG47QZ/website:faq-json into main 2025年12月19日 13:16:18 +01:00
Contributor
Copy link

Closes #468

Signed-off-by: IXVG47QZ

Closes https://codeberg.org/comaps/website/issues/468 Signed-off-by: IXVG47QZ
add json-ld faq schema
All checks were successful
Check site validity / Check Zola build (pull_request) Successful in 17s
dco / check (pull_request) Successful in 5s
274a0f019b
Signed-off-by: IXVG47QZ <jako_accomm@simplelogin.com>
Author
Contributor
Copy link

I wish it was possible to just do:

{%- for faq_page in terms.pages -%}

but it doesn't seem to work.

I wish it was possible to just do: `{%- for faq_page in terms.pages -%}` but it doesn't seem to work.
gedankenstuecke left a comment
Member
Copy link

I'm not sure that this is the right use (at least according to the guidelines Google gives for this):

Valid use cases: Both the question and answer are visible on the page.
Invalid use cases: The user can't find the FAQ content on the page at all.

In our case, the users can't actually read the FAQ answers on that page but need to click through to the corresponding pages

I'm not sure that this is the right use (at least according to the [guidelines Google gives for this](https://developers.google.com/search/docs/appearance/structured-data/faqpage)): ``` Valid use cases: Both the question and answer are visible on the page. Invalid use cases: The user can't find the FAQ content on the page at all. ``` In our case, the users can't actually read the FAQ answers on that page but need to click through to the corresponding pages
Author
Contributor
Copy link

In one sense it doesn't matter to follow Google's requirements, because this won't show up in the rich results anyway (it's restricted to health care and government), but on the other hand if Google says it, it can be seen as a best practice.

I'm thinking for AI readability, it would be good to have all the FAQ schema on one page, but we can also have individual FAQ schema on each FAQ page. That would improve the likelihood that ChatGPT and the like will find the right information.

In one sense it doesn't matter to follow Google's requirements, because this won't show up in the rich results anyway (it's restricted to health care and government), but on the other hand if Google says it, it can be seen as a best practice. I'm thinking for AI readability, it would be good to have all the FAQ schema on one page, but we can also have individual FAQ schema on each FAQ page. That would improve the likelihood that ChatGPT and the like will find the right information.

I'd say let's put them on the individual pages then, that way we also don't overload the index/list page!

I'd say let's put them on the individual pages then, that way we also don't overload the index/list page!
move faq schema to each individual faq page
All checks were successful
Check site validity / Check Zola build (pull_request) Successful in 17s
dco / check (pull_request) Successful in 5s
eb83b81a0a
Signed-off-by: IXVG47QZ <jako_accomm@simplelogin.com>
Author
Contributor
Copy link

Done. Should be good to go!

Done. Should be good to go!
gedankenstuecke left a comment
Member
Copy link

Very nice, tested locally as well 👍

Very nice, tested locally as well 👍
Sign in to join this conversation.
No reviewers
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
comaps/website!493
Reference in a new issue
comaps/website
No description provided.
Delete branch "IXVG47QZ/website:faq-json"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?