Google reports use of frames. The site doesn't use them

Support
,
1

Hi, google is punishing my site: konstytucja.online for using frames, but I am not using any frames/iframes. I suppose that it’s caused by Netlify masked DNS of some sort, but I have no idea how to fix this. I am using the free plan. My website is prerendered Vue + Nuxt site. I cannot add any namecheap DNS records, because I picked the netlify name server. Could someone please help me with this? As attachments, I am sending screens of google search, namecheap configuration and netlify configuration. Best, MZ

googe_namecheap_netlify_config
googe_namecheap_netlify_config.png1416×3914 749 KB

2

Just out of curiosity, are you using a tool to get search results like that, with the green and yellow success / warnings? Or is it just so by default?

3

It is the Bitdefender (antivirus) thing. It has web shield of some sort and flags websites as safe etc.

image
image.png784×711 57.5 KB

4

@futuregerald any ideas?

5

@luke any ideas? :< :<

6

hi @mzalevski - glad you found us here in community. :slight_smile:

first off, we need additional information in order to be able to help out - this post is a great start

additionally, which browser are you using?

7

@perry hi :slight_smile: I got the same results on safari, chrome, firefox, brave, opera and edge.
Update: Today I switched from Netlify DNS (redirect from namecheap to netlify nameserver) to “external dns” - pointing to netlify load balancer with A Record. So at the moment I am waiting for google crawler to acknowledge this. As I’ve written I guess that “frame” is comming from netlify dns records. I will come back with more info tommorow. Best, MZ

8

sounds good, @mzalevski! please keep us informed :slight_smile:

9

@perry unfortunately, google still considers my konstytucja.online as “frame using” :confused:

11

@mazdak78 - I am not sure what is causing this, I think it might be something to do with the metadata information in your site.

Can you try keeping all the DNS settings the same, but updating with a simple one-page html page instead of your vue + nuxt site and see if the issue is still present?

12

@perry, I’ve just uploaded simple website https://maciej-zalewski.pl
If, everything will be alright it’ll mean that the problem may have something to do with robots / sitemap I wrote (I kept them the same on both websites):

robots.txt:

Sitemap: https://maciej-zalewski.pl/sitemap.xml
User-agent: *
Disallow:
Disallow: /cgi-bin/

sitemap.xml:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="https://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://maciej-zalewski.pl</loc>
    <priority>1.0</priority>
    <changefreq>daily</changefreq>
    <lastmod>2019-11-13</lastmod>
  </url>
</urlset>
13

@mzalevski, frames are only defined in HTML files not in DNS records.

There are two key points I want to make:

  • DNS records do not change HTML files.
  • Netlify does not modify site content (with some small exceptions noted below).

First, I’m not aware of any possible ways for DNS records to affect or modify the contents of an HTML file served by Netlify. This simply doesn’t happen.

Second, we don’t modify the files hosted on our services. There are two exceptions: snippet injection and asset optimization. Neither of those will create a frame in your HTML though. Not unless you have a frame in a snippet you inject and, if this is the case, you are adding the frame - not Netlify. You are the person telling Netlify what to inject - so the frame in that case must be your creation.

I decided to investigate further. One can see what Google saw by viewing the cached version of the page for that search result:

http://webcache.googleusercontent.com/search?q=cache:DmalLlhDbZEJ:konstytucja.online/&hl=en&gl=us&strip=0&vwsrc=1

This is the “view source” version of the content that Google cached:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">
<html>
    <head>
        <meta http-equiv='content-type' content='text/html; charset=UTF-8'>
        <meta name="KEYWORDS" content="">
        <meta name="DESCRIPTION" content="">
        <meta name="VERSION" content="">
        <link href="" rel="shortcut icon" type="image/x-icon">
        <title></title>
    </head>
    <frameset rows='100%, *' frameborder=no framespacing=0 border=0>
        <frame src="https://clever-swartz-4cae5c.netlify.com/" name=mainwindow frameborder=no framespacing=0 marginheight=0 marginwidth=0></frame>
    </frameset>
    <noframes>
        <h2>Your browser does not support frames. We recommend upgrading your browser.</h2><br><br>
        <center>Click <a href="https://clever-swartz-4cae5c.netlify.com/" >here</a> to enter the site.</center>
    </noframes>
</html>

There is a frame in the HTML above. This is why Google says this - it is a quote from the HTML itself “Your browser does not support frames”. Google is quoting the website - not punishing it. This is what the site contained at that time.

At what time, you ask? Quoting that page:

This is Google’s cache of http://konstytucja.online/. It is a snapshot of the page as it appeared on Oct 25, 2019 03:55:49 GMT.

I checked the logs for our service for all of October 24th through and including October 26th. We served zero requests for this domain name at that time.

The message was in the HTML of the site itself and the site content above was not served by Netlify.

1 Like
16

thanks @luke !

on 25 October the site was served by Netlify:
<center>Click <a href="https://clever-swartz-4cae5c.netlify.com/" >here</a> to enter the site.</center>
but at the time I tried to redirect from konstytucja.online to this clever-swartz URI simply by masked redirect (hence the frame). I did not know that the google search results are mentioning the old redirect though.

Thanks again guys. I think I can take it from here. I need to make google see new frameless version of the website.

1 Like