16. Web fonts fail for Googlebot — Low
Search Console page resources: PrajavaniTextRegular.woff2, PrajavaniTextSemibold.woff2, PvHeadlineSemibold3.woff2, Roboto Slab → "Other error". Google often skips fonts; no indexing impact expected. ℹ️ (robots.txt Disallow: /*.woff$ affects .woff only, not .woff2.)
Likely cause found (16 Nov 2026): the font files are not fonts. In a desktop Chrome console on a PV article (user, 16 Nov 2026): Failed to decode downloaded font: https://www.prajavani.net/tpml/assets/ebd8d869f9071312fbd0.woff and …/3f9cbec7131a3db6b491.ttf, each with OTS parsing error: invalid sfntVersion: 1702391919. 1702391919 = hex 6578706F = the text "expo": the files start with export …, i.e. a JavaScript module saved under a font name, not a font.
- Why: PV's
webpack.config.js:27-31handles fonts with the oldfile-loader(name: "[name].[ext]"), while the webpack 5 build in@quintype/buildalso processes the same files as assets. The two together writefile-loader's JS output (export default __webpack_public_path__ + "…") into a hashed asset (<hash>.woff): a known webpack 5 +file-loaderconflict. The named.woff2entries (quintype-build.config.js:38-40, used bylayout.ejs:288-307) are separate; which stylesheet references the hashed.woff/.ttfstill needs confirming (not in the repo's own@font-facerules). - Impact: those font requests fail for every reader (not only Googlebot) and the browser falls back to another font; possible layout shift when fonts swap (#15).
- 🛠️ Fix: in the font rule add
type: "javascript/auto"(keepsfile-loaderworking under webpack 5) or replace it withtype: "asset/resource"and dropfile-loader. Verify:curl -s <font url> | head -c 4returnswOFF/wOF2(or���for TTF), and the console shows no font decode errors.