How to Use GeoDirectory Snippet Variables in Yoast?

By default, GeoDirectory can handle its own meta data for pages and CPTs.

However, if you are using Yoast SEO for adding meta title and description to GeoDirectory pages, you will need to use _gd_ prefix for all GeoDirectory snippet variables. 

Working with GeoDirectory Snippet Variables

Generally, you will need to use the custom snippet variables when adding meta data for your content using the GeoDirectory plugin. You can tweak this in the Settings --> General (tab) --> Titles & Meta (sub-tab) section.
However, if you have Yoast SEO plugin installed, it will take over the GeoDirectory meta settings by default. In this case, titles will still be used from the GeoDirectory settings, but not meta. You can disable this feature from the Titles & Meta page, as under:

Using Yoast SEO for GeoDirectory Snippet Variables

To manage the meta data for content types using Yoast SEO plugin, you will need to go to the Yoast settings section, located at SEO --> Search Appearance --> Content Types. Herein, you will find all the CPTs of GeoDirectory where you can add custom titles and meta info. 

To render GeoDirectory custom fields and variables properly using Yoast SEO meta, the _gd_ prefix is necessary.

You can specify the custom snippets for titles and meta here, with the _gd_ prefix. 

Here is how the _gd_ prefix for GeoDirectory variables will work when used in Yoast SEO plugin: 

  • %%in_location_single%% variable in GeoDirectory will be %%_gd_in_location_single%% in Yoast
  • %%category%% variable in GeoDirectory will be referred to as %%_gd_category%% in Yoast
  • %%location_city%% variable in GeoDirectory will become %%_gd_location_city%% in Yoast

Similarly, any GeoDirectory custom field too will need to be prefixed by _gd_ when working with Yoast SEO. For example, if you have a GeoDirectory custom field %%_zip_locality%% it will be referred to as %%_gd_zip_locality%% for Yoast. 

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.