Repository navigation
fix: Bing Site Scan findings (report page, slide template, DSOC project pages, export link) - #101
Merged
Merged
Conversation
… search Bing's Site Scan flagged both files for a missing meta description. The 2025 impact report is a public page, so it gets a description built from its own numbers, a canonical address and share tags. The session slide template is a file speakers download, with four h1 tags by design. It now answers with X-Robots-Tag: noindex instead of being polished for search.
The export address is under /api/, which robots.txt blocks on purpose, so Bing reported it as blocked. rel=nofollow tells crawlers not to go there.
A project page was rendered entirely in the browser, so crawlers got an empty shell with no h1 (reported by Bing's Site Scan) and every project shared the list page's title and canonical address. The page now reads the project on the server and passes it to the same view, so the first HTML holds the project. Each project has its own title, description and canonical address, and is cached for an hour. - The built-in samples repeat real projects and stand in when the database is unreachable, so they are marked noindex. - If the database cannot be read, the browser loads the project as before and the page is not marked noindex. - Dates are shown in UTC, as stored, so the server and the browser print the same day. Visitors west of UTC used to see the previous day. - Mentor email addresses are not put in the page; it never showed them.
Now that project pages can be read by search engines, the active projects from the database are listed with the date each last changed. The sitemap is rebuilt hourly, so a new project appears without a deploy.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Bing's Site Scan of www.devweekends.com (37 pages) reported 3 errors, 6 warnings and 3 notices. The image alt findings were already fixed by earlier PRs. This fixes the four that were still true on the live site.
Findings and fixes
1.
/reports/fellowship-2025-impact-report.html: no meta description. It is a public report, so it gets a description built from its own numbers, a canonical address and share tags.2.
/brand/session-template.html: no description, four h1 tags. It is a slide template speakers download, not a page for search. It now sendsX-Robots-Tag: noindex. The file itself is unchanged.3.
/dsoc/projects/pathmentand/dsoc/projects/voiceybill: no h1. Project pages were rendered entirely in the browser, so a crawler got an empty shell.noindex, so search shows only the real project pages.noindex.4.
/api/feed/export: blocked by robots.txt. The block is deliberate. The link on/feednow hasrel="nofollow"so crawlers are not sent to an address they may not fetch.Checked on a local production build