Remove image_url related error appearing during structured data testing

By Blogger
So your blog has structured data and now want to make sure that the web crawlers should also understand that you have placed structured data on your blog. The best way to make sure that is to test your blog URL using https://search.google.com/structured-data/testing-tool. This is not a validator of the tags in your blog but a tool, using which Google makes sure it can read structured data from the page and if required can appear as a rich card in a search result.

If you have a blog on Blogger and have validated it using the Google structured data testing tool, there are chances that you might have seen below error:
The property postId is not recognised by Google for an object of type BlogPosting.

Below are the steps to how to remove postId related error appearing during Structured data testing.
  1. Go to Blogger.com
  2. Select the Blog in which you want to make the change.
  3. Click "Template" in the left menu.
  4. Click on "Edit HTML"
  5. Once the HTML editor appears, click inside the editor and press Ctrl+F. This will show a search box appear on the top right corner of the editor as below:
  6. Paste the following code in the search box and hit enter to find it.
    <meta expr:content='data:post.firstImageUrl' itemprop='image_url'/> The code could appear as below: <b:if cond='data:post.firstImageUrl'> <meta expr:content='data:post.firstImageUrl' itemprop='image_url'/> </b:if>
  7. Once you find the code comment it out as below:
    <!--<b:if cond='data:post.firstImageUrl'> <meta expr:content='data:post.firstImageUrl' itemprop='image_url'/> </b:if>-->
  8. Save the template.
You can again test your blog URL at https://search.google.com/structured-data/testing-tool. This time the error for postId will not appear.


Below are the links to fix other errors and warnings appearing during structured data testing:
A value for the headline field is required.
A value for the url field is required.
A value for the image field is required.
A value for publisher field is required.
The dateModified field is recommended. Please provide a value if available.
The mainEntityofPage field is recommended. Please provide a value if available.
The property postId is not recognised by Google for an object of type BlogPosting.
The property blogId is not recognised by Google for an object of type BlogPosting.

Make Money from Surveys

Make money by filling online surveys

Popular posts from this blog

Schema.Object has an unresolved reference to Schema

By Blogger
If while building a database project face this error: Severity Code Description Project File Line Suppression State Error SQL71501: Function: [schema].[object] has an unresolved reference to Schema [schema]. DBProject.Database D:\TFS\path\DBProject.Database\schema\Functions\schema.object.sql Then this error might be because you have object definition referring to the schema under which they are supposed to be created but there is not script to create that schema. Suppose your schema name is empschema then you should add file smpschema.sql to the project with following code: CREATE SCHEMA empschema AUTHORIZATION dbo;
... more »

The current master key cannot be decrypted

By Blogger
We had the requirement to migrate our cluster to a different domain. We knew that Microsoft does not recommend to migrate the existing cluster to a different domain (Read http://support.microsoft.com/kb/269196 ). The business could not afford the time to build a new cluster in the target domain and move the databases to the SQL Server instance created on target cluster. We uninstalled the SQL server after backing up each database. Server team removed the nodes from the cluster and then moved each node to a new domain. We then installed the SQL Server and attached (since time was constraint) each databases back. All the databases were running fine and we could use them. We restored the master and msdb database so that all the logins, jobs and integration packages are back in place. Later while setting up distribution for replication we faced the first error: There is no remote user 'distributor_admin' mapped to local user '(null)' from the remote server 'repl_dist...
... more »

Error for system versioned tables while importing to SQL Server 2012

By Blogger
What does this error mean: Error SQL72014: .Net SqlClient Data Provider: Msg 102, Level 15, State 1, Line 10 Incorrect syntax near 'GENERATED'. CREATE TABLE [dbo].[TableName] (....... On your SQL Azure database from where the export is taken, the table for which the error is shown has system versioning turned on. Following is the code to turn off the system versioning on the table: In case if you want to drop the columns associated with versioning you may run following code to first drop the constraint on both the columns and then drop the columns: ALTER TABLE [dbo].[TableName] DROP CONSTRAINT [DF_SysEnd]; ALTER TABLE [dbo].[TableName] DROP CONSTRAINT [DF_SysStart]; ALTER TABLE [dbo].[TableName] DROP COLUMN [SysStartTime]; ALTER TABLE [dbo].[TableName] DROP COLUMN [SysEndTime]; Note: The constraint names and column names could be different in your case.
... more »