Definitive Guide to SEO with Wappler

[markoax21]

Hello everybody, I searched everywhere in the posts but I did not find a definitive solution to my problem: make sure that my dynamic pages are indexed correctly by Google.
I work with ASP.net and MSSQL
The pages work correctly but I realized that dynamic titles and descriptions are not considered by Google.
I tried to force tag like that:

<title> {{metadata.data.query[0].metadataTitle}}</title>
<meta name="description" dmx-bind:content="metadata.data.query[0].metadataDescription">

I ask you for help on how to deal with the problem without switching to Nodejs (I tried it, but I have other types of errors and especially would not want to redo the work already done).
Should I focus on Rewrite URLs? This could solve my problems? I tried this too but I wasn’t sure I was on the right track so I let it go.

Can anyone help me? Thank you!

[Teodor]

@markoax21

The pages work correctly but I realized that dynamic titles and descriptions are not considered by Google.

They actually are indexed and rendered correctly by Google. Probably you don’t have the app root set to the whole page, but to the body instead.

[TMR]

I dont think full SEO and Wappler combined with .NET is a good mix, I’ve had similar issues with this.

Heres the thread:

Dynamic Opengraph Meta Tags in a .NET site

Hi all, Sheesh, this one has been difficult to work out - has anyone managed to get dynamic Opengraph meta tags to work on a .NET Windows server…? My App Root is set to ‘Page’ and the main title tag is showing dynamic data when shared to Facebook but the rest are just showing the code, here’s what my code looks like: <title>{{scMetaTags.data.querySeo.SeoTitle}} </title> <meta name="og:site_name" dmx-text="scMetaTags.data.querySeo.SeoOgSitename"> <meta name="og:title" dmx-text="scMetaTags.data…

We use .NET with MariaDB. A powerful way to promote any website is by allowing users to share what they’re seeing, if we create a live data page in Wappler and we cant allow users to share what were creating it means big problems for us, and anyone else who wants to do the same.

We decided against the prerender service as its $99 per month for each site we deploy it on.

Our only other option is to use .NET code directly on the page instead of App Connect expressions, which kind of defeats the purpose of using Wappler for us. We’re currently rewriting a lot of our content to make up for this shortfall.

We have NodeJS projects starting so there’s no problem there but our core is .NET and always will be.

[Teodor]

@TMR that’s a different topic. You’re referring to Facebook not being able to render javascript expression in the meta tags. The topic here is about Google and google renders and reads these expressions witout any issue.

[JonL]

@TMR

We decided against the prerender service as its $99 per month for each site we deploy it on.

Prerender is FOSS.

GitHub - prerender/prerender: Node server that uses Headless Chrome to render...

[markoax21]

I really don’t want to ask the customer to spend money on that kind of service!
I would expect to be able to handle the problem in wappler or somehow, but in a simple way.
I can’t change programming language
With rewrite url I could get similar results or improvements?

[Teodor]

Marko, as i explained in my first reply:

@Teodor

They actually are indexed and rendered correctly by Google. Probably you don’t have the app root set to the whole page, but to the body instead.

The rest mentioned by @TMR is something totally different.

[markoax21]

@Teodor

They actually are indexed and rendered correctly by Google. Probably you don’t have the app root set to the whole page, but to the body instead

Thank you teo, sorry if I do not explain well.
I have difficulty indexing the details pages.
In my website I have a page called “events” with a data detail that makes a normal query.
That page is indexed.
Clicking on each event you go on “events-details2.aspx? id=XXX”. I can’t get those pages indexed to Google.
Root apps are always set to “page”, I don’t have blocks on robots.txt or sitemap.xml

[Teodor]

@markoax21

I can’t get those pages indexed to Google.

What do you mean you can’t get them indexed? Is there any specific problem?

[TMR]

In disagree, the topic is about SEO (in the title), Google is mentioned but the crux of the issue is the way Wappler deals with SEO. My point being that Facebook marketing is vital for a huge amount of websites, and a major SEO benefit, yet Wappler deals with it badly in a .NET environment.

[markoax21]

@Teodor

What do you mean you can’t get them indexed? Is there any specific problem

I mean that if I’m searching for the same word (for example, the title of the event), Google it only returns the “events.aspx” page and not the relative page “event-details page?ID=XXX”

[Teodor]

@TMR can you please stick to the current topic - which is about some pages for @markoax21 not being indexed? Your facebook issues have nothing to do with this one, please open a separate topic if you need to discuss these.

[Teodor]

@markoax21

I mean that if I’m searching for the same word (for example, the title of the event), Google it only returns the “events.aspx” page and not the relative page “event-details page?ID=XXX”

Well are these pages linked somewehere on some page in your site? If there are no links to them, how would google know about the existence of these pages? Also have you checked the google search console tools to see how your pages are performing?
A page missing from google search results can be 1000 different things …

[markoax21]

@Teodor

Well are these pages linked somewehere on some page in your site? If there are no links to them, how would google know about the existence of these pages? Also have you checked the google search console tools to see how your pages are performing?
A page missing from google search results can be 1000 different things …

Sure, the details pages are all linked from the main page through buttons, with syntax like:

<a class="button-primary" dmx-on:click="browser1.goto(metadataPathName)">
<font color="#000000"> DETAILS </font>
</a>

[Teodor]

But that’s not a real link, it’s a click event that redirects to somewhere … why not use href, so that the search engine knows that’s a link and index the url it points to?

dmx-bind:href="metadataPathName"

[markoax21]

Like that could works?

<a class="button-primary" dmx-bind:href="'eventi2.aspx?id='+ID">
 <font color="#000000"> DETAILS </font>
</a>

[Teodor]

Yes, this is how a link should be used - with a href attribute, this way the search engine knows that this i a link and will follow the href.

[markoax21]

After making this link change, I went to google search console to do some testing.
The page is indexed

https://www.villarperosa.net/eventi2.aspx?id=629

But I noticed that in “real time test” of this page doesn’t display dynamic texts
Where event date and event title should appear

…actually google’s real-time test fails to read the fields

I checked the same in old sites made in ASP with Dreamweaver and this does not happen: where there are dynamic fields, in search console I see the corresponding queries

(details page of a different site, but with the same type of query)

[Teodor]

@markoax21

…actually google’s real-time test fails to read the fields

I can’t really recreate this. I have quite a few sites in the google search console and Live Test shows all the dynamic data on all the indexed pages.
Are you sure there are no any errors in your browser dev tools?

[markoax21]

OK I’ll do other tests to understand more. In fact on a Google Chrome gives me this problem, on another browser instead no.