@PhilAre As a seasoned SharePoint administrator, I've encountered similar challenges in the past, and I have a few suggestions that may help resolve this issue. First, let's ensure the site columns are properly configured. Double-check that the data types and settings are correct, and that the columns are published and readily available for use in the page library. Sometimes, minor configuration tweaks can make all the difference. Next, I'd recommend adding some test values to the site columns on a few sample pages in the page library. This can help trigger the crawling process and make the columns visible as crawled properties.
Once you've done this, you can manually request a reindex of the page library to ensure the changes are reflected. Now, let's consider the content type configuration. Have you tried creating a new content type that inherits from the "Site Page" content type and adding the site columns to that new content type? This approach can sometimes help the site columns become properly crawled, as the search engine may have an easier time indexing the data. Additionally, it's worth double-checking the search configuration for your site. Ensure that the page library is included in the appropriate search scope and that the managed property settings are correctly mapped to the site columns.
If none of these suggestions resolve the issue, you may want to consider an alternative approach using the PnP Modern Search web part with a search-driven page library. In this scenario, the pages are stored in a separate document library, and the page library is used only for navigation. This can sometimes work around the challenges you're facing with site columns not being properly crawled in the page library.
I understand that this issue can be quite frustrating, but I'm confident that with a thorough investigation and some strategic adjustments, we can find a solution that works for your organization. Please feel free to reach out if you have any additional questions or need further assistance.
