Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Comparison between raw html and prerender outputs

Open
#188 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

Reproduce the three reported views for https://www.ailearn.io: the prerender.io raw HTML page, the service.prerender.io response, and the Search Console rendering. Compare their cached HTML and rendering behavior to determine whether the discrepancy is reproducible; done means identifying the cause and documenting a specific resolution, but no project file or test is named.

Written by the indexing model from the issue text.

Description

Hi,

Just signed up for prerender and having a bit of an issue. My website is https://www.ailearn.io. When I go to prerender.io and look at the raw html cached on prerender (https://prerender.io/raw-html?url=https%3A%2F%2Fwww.ailearn.io&adaptiveType=desktop), this looks to be slightly out of date when I compare it to the current site (e.g., style sheet is relative reference in the raw vs absolute on the homepage. Even after recaching, this doesn't seem to change? What's the reason for this?

When I then use https://service.prerender.io/https://www.ailearn.io, the output looks v different from the raw html - I think this is because of the relative references, but these have now been removed, so I'm hopeful that should solve this problem.

Finally, when I use the search console to render my page, I get a blank screen - do you have any advice as to what's causing this?

Many thanks,
J

Dominant language
JavaScript
Stars
921
Forks
185
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from prerender/prerender-node

All issues in prerender/prerender-node

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.