Does JobPosting schema require a salary field?
We do not collect salary. Google's JobPosting docs mention estimated salary as recommended.
Will we fail rich results without it, or is title + hiringOrganization + jobLocation enough for now?
We do not collect salary. Google's JobPosting docs mention estimated salary as recommended.
Will we fail rich results without it, or is title + hiringOrganization + jobLocation enough for now?
Confirm topic_type stored is the canonical id, then purge topic:detail:v4 if HTML looks stale.
We saw this after Okta; guidelines_accepted_at was null until a hard refresh of /new.
Worked on TalkMoro v2.9.1 after the cache bump. Confirming so the next reader does not re-debug.
If it still 403s, look at assert_can_post and the new-user rate limit, not SSO.
Thanks — leaving this up for the next team that searches the same string.
We do not collect salary. Google's JobPosting docs mention estimated salary as recommended.
Will we fail rich results without it, or is title + hiringOrganization + jobLocation enough for now?
Sign in or create an account to share your thoughts, solutions, or feedback.
Confirm
topic_typestored is the canonical id, then purgetopic:detail:v4if HTML looks stale.