Is bad for SEO if browser need to run synchronous JS to get content?
up vote
1
down vote
favorite
I'm developing a site using symfony + Vue. The problem is that this HTML with non-standard tags (components) gets into the browser.
All that contained in the <div id="app"> element must process JS to get browser-friendly content with standard tags.
These components would not exist if I used server rendering (SSR), but here I don’t understand a bit: during loading, my page already has all the content needed, no API calls are made to get the content like in SPA.
Is it necessary to use server rendering in this case? Is it bad for SEO that before you get normal content, you need to execute JS code for this.
As far as I know, Google and Bingo index synchronous JavaScript well.
seo google-search search-engines web-crawlers javascript
asked 4 hours ago
Илья Зеленько
1203
New contributor
Илья Зеленько is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
1
down vote
favorite
I'm developing a site using symfony + Vue. The problem is that this HTML with non-standard tags (components) gets into the browser.
All that contained in the <div id="app"> element must process JS to get browser-friendly content with standard tags.
These components would not exist if I used server rendering (SSR), but here I don’t understand a bit: during loading, my page already has all the content needed, no API calls are made to get the content like in SPA.
Is it necessary to use server rendering in this case? Is it bad for SEO that before you get normal content, you need to execute JS code for this.
As far as I know, Google and Bingo index synchronous JavaScript well.
seo google-search search-engines web-crawlers javascript
asked 4 hours ago
Илья Зеленько
1203
New contributor
Илья Зеленько is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm developing a site using symfony + Vue. The problem is that this HTML with non-standard tags (components) gets into the browser.
All that contained in the <div id="app"> element must process JS to get browser-friendly content with standard tags.
These components would not exist if I used server rendering (SSR), but here I don’t understand a bit: during loading, my page already has all the content needed, no API calls are made to get the content like in SPA.
Is it necessary to use server rendering in this case? Is it bad for SEO that before you get normal content, you need to execute JS code for this.
As far as I know, Google and Bingo index synchronous JavaScript well.
seo google-search search-engines web-crawlers javascript
asked 4 hours ago
Илья Зеленько
1203
New contributor
Илья Зеленько is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I'm developing a site using symfony + Vue. The problem is that this HTML with non-standard tags (components) gets into the browser.
All that contained in the <div id="app"> element must process JS to get browser-friendly content with standard tags.
These components would not exist if I used server rendering (SSR), but here I don’t understand a bit: during loading, my page already has all the content needed, no API calls are made to get the content like in SPA.
Is it necessary to use server rendering in this case? Is it bad for SEO that before you get normal content, you need to execute JS code for this.
As far as I know, Google and Bingo index synchronous JavaScript well.
seo google-search search-engines web-crawlers javascript
seo google-search search-engines web-crawlers javascript
asked 4 hours ago
Илья Зеленько
1203
New contributor
Илья Зеленько is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 hours ago
Илья Зеленько
1203
New contributor
Илья Зеленько is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 hours ago
Илья Зеленько
1203
New contributor
Илья Зеленько is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 hours ago
Илья Зеленько
1203
asked 4 hours ago
Илья Зеленько
1203
1203
New contributor
Илья Зеленько is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Илья Зеленько is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Илья Зеленько is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
Google doesn't care about the name of the tags in your body section - the crawler renders the site using chrome itself (including synchronous js) so it cares for whatever is printed to the screen. You're safe as long as your tags in the head are standard.
It is just safer to have SSR to reduce possible errors (timeouts, things that appear only on interaction, etc..)
But you can check and see what google sees using the google fetch bot:
https://www.google.com/webmasters/tools/googlebot-fetch
answered 2 hours ago
bArmageddon
1462
New contributor
bArmageddon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "45"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Илья Зеленько is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f119735%2fis-bad-for-seo-if-browser-need-to-run-synchronous-js-to-get-content%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Google doesn't care about the name of the tags in your body section - the crawler renders the site using chrome itself (including synchronous js) so it cares for whatever is printed to the screen. You're safe as long as your tags in the head are standard.
It is just safer to have SSR to reduce possible errors (timeouts, things that appear only on interaction, etc..)
But you can check and see what google sees using the google fetch bot:
https://www.google.com/webmasters/tools/googlebot-fetch
answered 2 hours ago
bArmageddon
1462
New contributor
bArmageddon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
3
down vote
accepted
Google doesn't care about the name of the tags in your body section - the crawler renders the site using chrome itself (including synchronous js) so it cares for whatever is printed to the screen. You're safe as long as your tags in the head are standard.
It is just safer to have SSR to reduce possible errors (timeouts, things that appear only on interaction, etc..)
But you can check and see what google sees using the google fetch bot:
https://www.google.com/webmasters/tools/googlebot-fetch
answered 2 hours ago
bArmageddon
1462
New contributor
bArmageddon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Google doesn't care about the name of the tags in your body section - the crawler renders the site using chrome itself (including synchronous js) so it cares for whatever is printed to the screen. You're safe as long as your tags in the head are standard.
It is just safer to have SSR to reduce possible errors (timeouts, things that appear only on interaction, etc..)
But you can check and see what google sees using the google fetch bot:
https://www.google.com/webmasters/tools/googlebot-fetch
answered 2 hours ago
bArmageddon
1462
New contributor
bArmageddon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Google doesn't care about the name of the tags in your body section - the crawler renders the site using chrome itself (including synchronous js) so it cares for whatever is printed to the screen. You're safe as long as your tags in the head are standard.
It is just safer to have SSR to reduce possible errors (timeouts, things that appear only on interaction, etc..)
But you can check and see what google sees using the google fetch bot:
https://www.google.com/webmasters/tools/googlebot-fetch
answered 2 hours ago
bArmageddon
1462
New contributor
bArmageddon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 hours ago
bArmageddon
1462
New contributor
bArmageddon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 hours ago
bArmageddon
1462
answered 2 hours ago
bArmageddon
1462
1462
New contributor
bArmageddon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
bArmageddon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
bArmageddon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Илья Зеленько is a new contributor. Be nice, and check out our Code of Conduct.
Илья Зеленько is a new contributor. Be nice, and check out our Code of Conduct.
Илья Зеленько is a new contributor. Be nice, and check out our Code of Conduct.
Илья Зеленько is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Webmasters Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f119735%2fis-bad-for-seo-if-browser-need-to-run-synchronous-js-to-get-content%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
