Website Verification Errors

Whether signing up for a new publisher account or adding a new traffic source to your account, you may occasionally come across an error message. To help get past these screens, we’ve compiled a list of error messages and potential solutions below.

General verification error messages

  • The connection to your server timed out.
  • We were unable to verify your file because we received a server timeout. This could be because your server is down or is busy and responding slowly. Make sure that your server is responding and try again.
  • We encountered an error looking up your site’s domain name.
  • We tried to access your verification file but were unable to access your domain due to a DNS error. This could be because your server is down, or there is an issue with the DNS routing to your domain. Make sure that your domain is resolving correctly and try again.
  • The download request was redirected too many times.
  • Check the URL for potential issues, such as an infinite loop.
  • Your server returned an invalid response.
  • This can happen if your site requires password authentication, or if we cannot access it for other reasons.
  • We were unable to connect to your server.
  • Make sure that your server is not down, and that your domain is resolving correctly, and try again.
  • An internal error occurred.
  • If this problem persists, contact us at [email protected].
  • I provided the wrong site or mistyped my website!

    If you need to change any information on your pending FlexOffers.com Publisher application, please send what you would like to change the information FROM and TO from the email address of the account owner we have on file to [email protected] Our compliance team will then be able to make those adjustments so that you can complete your FlexOffers.com Publisher application.

    I downloaded the verification file, but the file is empty!

    If you open the file in your browser, it may appear to be empty. It may be that the HTML code in that file is not visible in a browser unless you inspect the code. You can confirm the file is fine by opening it in your Notepad program, or by right-clicking in your browser and selecting View Page Source. The file contains the meta tag information we need to verify your site.

    I uploaded the file and/or changed the meta tag, but the verify button still won’t verify my site!

    No problem! We’ll have a FlexOffers.com team member take a closer look. Please send an email to [email protected] and provide your name and a link to the page you uploaded or changed.

  • NOTE – If your site was verified but no longer appears to be verified, make sure that the HTML file or meta tag you used to verify the site is still in place. Removing any of these can cause your site to become unverified, and you will need to go through the verification process again.

Meta tag verification errors

  • We couldn’t find the verification meta tag on your home page.
  • The verification meta tag must be within the<HEAD>section of the page. If you see this error, check the following:
    • Is the meta tag on the correct page? We look for it on your site’s homepage. This is the page that your server returns when someone requests your site (such as http://www.example.com/). This page is often named index.html or index.htm, but could be named differently, depending on your server’s configuration.
    • Is the meta tag in the correct place on the page? We look for it in the page’s HEAD section. An example of correct placement is shown below.
      <HTML>
                                         <HEAD>
                                         <TITLE>Your Title</TITLE>
                                         <meta name="fo-verify" content="String_we_ask_for">
                                         </HEAD>
                                         <BODY>
    • If you’re using a web editor or a WYSIWYG editor to edit your page, make sure you’ve selected the ‘Edit HTML’ option or are editing the source code of the page.
  • Your meta tag is incorrect.
  • We found the verification meta tag, but the contents were incorrect. To avoid errors, copy and paste the meta tag provided on the Verification page.
  • Your home page returns an HTTP status code of XXX instead of 200(OK).
  • If your server returns an HTTP status code other than 200(OK) for your home page, we will not be able to verify that it contains the expected meta tag.

HTML file verification errors

  • Your verification file was not found.
  • Please download the verification file provided on the Verification page and upload it to the specified location without any modifications. If the file name or content does not match the HTML file provided, we won’t be able to verify your site ownership.NOTE – In some cases when a browser downloads the same file multiple times it will add a number to the file name. Be sure to rename the file to remove the extra number (e.g. : fo-verify.html).
  • Your verification file has the wrong content.
  • Verification checks to see if your verification file has the same filename and content as the file provided on the Verification page. If the file name or content does not match the HTML file provided, we won’t be able to verify your site ownership. Please download the verification file provided on the Verification page and upload it to the specified location without any modifications.
  • Your verification file is empty.
  • Verification checks to see if your verification file has the same filename and content as the file provided on the Verification page. If the file name or content does not match the HTML file provided, we won’t be able to verify your site ownership. Please download the verification file provided on the Verification page and upload it to the specified location without any modifications.
  • Your verification file returns an HTTP status code of XXX instead of 200(OK).
  • If your server returns an HTTP status code other than 200(OK) for your HTML verification file, we will not be able to verify that it has the expected filename and content.
  • The download request was redirected too many times.
  • If your site directs traffic to another site, we recommend using the meta tag verification method instead.
  • Your verification file redirects to a disallowed location.
  • We will not follow redirects for verification files; if your site redirects all traffic to another site, we recommend using meta tag verification. Redirects within a single site—for example, from http://example.com/ and to http://www.example.com/—are allowed.

 

How do I verify my free blogging site?

If you are using the free version of WordPress, WIX, Blogger, Blogspot or other blogging websites on your publisher application, then our normal “meta tag verification” of your website may not work. Instead, you will need to go through a manual verification process (See: “If all else fails” below).

 

Can you still verify my website if it’s under construction?

Unfortunately, per the policies set in place by our compliance department, we can’t accept sites in development or under construction. However, we can examine your application again when your website is complete.

Email our team at [email protected] with a link to the completed website when you are ready for us to review it.

 

IF ALL ELSE FAILS WHEN TRYING TO VERIFY YOUR WEBSITE:

Let’s try something else. Please place the word “flexoffers” someplace on your website and then send the link to that page to [email protected]. Our compliance team will then be able to manually verify your website.

After your website has been verified by our compliance team, you will receive a notification from our system with the results of your review. At that point, you can remove the word “flexoffers” from your site. We do not recommend removing “flexoffers” before receiving the results of your review to ensure our compliance team finds it and can move forward with your application review.