{"id":22491,"date":"2016-07-10T00:29:30","date_gmt":"2016-07-10T00:29:30","guid":{"rendered":"https:\/\/wpgeodirectory.com\/docs\/?p=22491"},"modified":"2016-07-17T13:09:42","modified_gmt":"2016-07-17T13:09:42","slug":"manage-location","status":"publish","type":"post","link":"https:\/\/wpgeodirectory.com\/docs\/manage-location\/","title":{"rendered":"Location Manager – Manage Location"},"content":{"rendered":"

These are the sections\u00a0you will find when you install the Location Manager:<\/h4>\n

Introduction and Location Settings tab<\/a> – Manage Location tab<\/strong> – SEO Settings tab – Add\/Edit Location tab – Translate Countries tab<\/p>\n

On this page:<\/h4>\n

Introduction<\/a> – City Neighbourhoods<\/a>\u00a0– Adding or editing locations<\/a>\u00a0– Merging locations<\/a><\/p>\n

<\/a>Introduction<\/h3>\n
    \n
  1. The Manage Location<\/strong><\/em> tab is where you can edit or merge locations, and add meta data for your location pages.<\/li>\n
  2. Here you can also divide locations into neighborhoods.<\/li>\n<\/ol>\n

    <\/a>City Neighborhoods<\/h3>\n
      \n
    1. Locations are based on the Google Maps API, and the size of cities (towns, suburbs or villages etc depending on the country) can vary greatly from country to country.\u00a0Your locations need to be therefore always city > region > country<\/strong><\/em>, exactly like Google suggests when you add a listing from the frontend.<\/li>\n
    2. In some countries, cities are divided into smaller sections, for example New York City is divided in the boroughs of\u00a0Bronx, Manhattan, Brooklyn, Queens and Staten Island.<\/li>\n
    3. The neighborhoods need to be manually added in the backend, and need to be manually selected by users adding listings.<\/li>\n<\/ol>\n

      Adding neighborhoods<\/h4>\n
        \n
      1. For this example we will add the New York City boroughs as GD neighborhoods.<\/li>\n
      2. At GD > Multilocations > Manage Location<\/strong><\/em> tab, find the city you want to add neighborhoods.
        \n\"\"<\/li>\n
      3. Click on the plus sign + and then click on Add Neighborhood:
        \n\"\"<\/li>\n
      4. Then add the name of the neighborhood, and Set neighborhood on map<\/strong><\/em>:
        \n\"\"<\/li>\n
      5. Keep adding all neighborhoods.<\/li>\n<\/ol>\n

        Location switcher<\/h4>\n
          \n
        1. Your visitors will now be able to filter locations by neighborhood:
          \n\"\"<\/li>\n<\/ol>\n

          Adding listings<\/h4>\n
            \n
          1. Your users will now be able so select the neighborhoods when adding listings:
            \n\"\"<\/li>\n<\/ol>\n

            <\/a>Adding or editing locations<\/h3>\n
              \n
            1. As part of your initial GD Core plugin, you should already have a default location<\/a> set.
              \nIt is one of the compulsory               basic installation steps<\/a>.<\/li>\n
            2. <\/i> Best practice is not to add locations here, because every location will have a page created and you will only end up with empty pages.
              \nWait for your users to add listings and locations will be automatically created\u00a0as your users add listings from the frontend.<\/li>\n
            3. There might be some occasions when you need to modify a location. For example a location has been added that does not conform to what the Google Map API<\/a> would have added, and you need to correct the spelling for example.<\/li>\n
            4. <\/i> Do not delete locations unless you have no listings in that location; deleting locations will delete all listings in the location!
              \n<\/span><\/li>\n<\/ol>\n

              City Meta and City Description<\/h4>\n
                \n
              1. Towards the bottom of the editing page for each location, you will find City Meta<\/strong><\/em> and City Description<\/strong><\/em> fields.
                \nEnter your data (you can use HTML in the City Description field):
                \n\"\"<\/li>\n
              2. The City Meta<\/strong><\/em> data will now be added to the source of the relevant location page:
                \n\"\"<\/li>\n
              3. <\/i> This information is also used for the\u00a0GD > Location Description<\/strong><\/em> widget.<\/a><\/li>\n<\/ol>\n

                <\/a>Merging locations<\/h3>\n
                  \n
                1. Sometimes your users add locations to your database using different spelling than a location already in your database (for example LasVegas, Texas, US<\/strong><\/em> instead of Las Vegas, Texas, United States<\/strong><\/em>).<\/li>\n
                2. Your GD database will treat this as two different locations.<\/li>\n
                3. There is a tool to merge these two locations.<\/li>\n
                4. From\u00a0the Manage Locations<\/strong><\/em> tab, select the locations you want to merge.<\/li>\n
                5. Scroll to the bottom of the page, and click Merge<\/strong><\/em>.
                  \n\"\"<\/li>\n
                6. On the next page, select the correct location you want to keep, and then click Set Primary<\/strong><\/em>.
                  \n\"\"<\/li>\n
                7. That will re-assign the correct location to all your listings in any of the locations you merged.<\/li>\n
                8. <\/i> Do not delete a location because that will also delete any listings in that location!<\/span><\/li>\n
                9. <\/i> You can also use the above process to correct any of your locations: just add the correct location first and then merge with any incorrect locations.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

                  The Manage Location tab is where you can edit or merge locations, and add meta data for your location pages.
                  \nNeighborhoods are also explained here.<\/p>\n","protected":false},"author":1676,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[34],"tags":[],"amp_validity":null,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/posts\/22491"}],"collection":[{"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/users\/1676"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/comments?post=22491"}],"version-history":[{"count":0,"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/posts\/22491\/revisions"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/media?parent=22491"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/categories?post=22491"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/docs\/wp-json\/wp\/v2\/tags?post=22491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}