Comparison between raw html and prerender outputs

Abierto
#188 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
20/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
javascript
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
JavaScript
Estrellas
921
Forks
185
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de prerender/prerender-node

Todos los issues de prerender/prerender-node

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.