How to Refresh Website Thumbnails in a WordPress Directory Plugin

Start by identifying what the directory calls a “website thumbnail.” It may be a screenshot fetched from a listing’s website URL, an uploaded listing photo or logo, or an old cached version of the directory page. Each has a different refresh path: fix or recapture the source screenshot, replace or reorder the listing image, regenerate image-size derivatives, or clear the relevant cache.

The title does not name a directory plugin, so the steps below use GeoDirectory as a documented example. Other plugins may use different fields, controls, and screenshot services. Check your installed plugin’s documentation before assuming its controls match GeoDirectory’s.

1. Identify the thumbnail’s source

Open the listing and determine whether the image is a preview of an external website or an image uploaded to the listing. If you cannot tell, inspect the rendered image URL in your browser’s developer tools: an image served from your WordPress media library is usually an uploaded image or derivative; a remote capture may be stored by the plugin or a third-party service. Also check whether the directory card is showing a fallback image.

What you see	Likely source	First place to check
A screenshot of the business’s website	A URL or screenshot field	The listing’s website URL, screenshot field configuration, and plugin’s capture workflow
A business photo or logo	Listing upload or custom image field	The listing’s uploaded images, featured-image order, and logo field
A correct image on the listing but an old image on the archive	Cached page or template selection	Page and CDN caches, then the archive template’s image settings
A blurry or oddly cropped image	Image-size derivative or selected size	WordPress media sizes, theme dimensions, and the card template

This distinction matters: regenerating WordPress thumbnails rebuilds image-size derivatives from images WordPress already has. It does not, by itself, recapture a remote website.

2. Refresh a website screenshot

For an external website preview, first verify the listing’s URL and how the installed plugin creates the preview. In GeoDirectory, its changelog records screenshot generation for URL fields by appending _screenshot to the field name, for example website_screenshot. Check that your field and listing data match the configuration expected by your installed version.

1. Open the listing’s edit screen and confirm the website URL is current, valid, and publicly reachable.
2. Check the URL field’s screenshot configuration. In GeoDirectory, confirm the relevant screenshot field naming and setup for your version.
3. Save the listing if you corrected its URL or field data, then check the listing and directory archive.
4. If the screenshot remains stale, consult the current documentation or support for that plugin and version. The available GeoDirectory documentation does not establish a universal manual “refresh now” button or recapture schedule.

Do not treat thumbnail regeneration as a remote screenshot refresh. A capture can also fail or show an unexpected page if the external site is unavailable, requires a login, redirects, or blocks automated requests. Verify the public URL and ask the plugin provider how its screenshot capture works before changing unrelated media settings.

3. Refresh an uploaded listing image or logo

If the card shows a listing photo, logo, or placeholder, correct the image attached to the listing first. GeoDirectory documents listing images as uploads associated with a listing; the first image is treated as the featured image, and images can be reordered by drag and drop. Its Post Images controls can display a featured image, logo, slider, gallery, or custom image field.

1. Edit the listing and confirm the intended photo or logo is present.
2. If the wrong photo is featured, reorder the images so the intended featured image is first.
3. Check the image-display setting or custom image field used by the directory card.
4. If a placeholder appears, check the configured fallback sources. GeoDirectory’s documented order includes company logo, first or featured uploaded image, category default image, custom post type default image, and archive default image.
5. Save and inspect both the listing and archive card.

GeoDirectory’s GD > Post Images documentation covers image display settings and image sources. It also notes that GeoDirectory does not process uploaded images itself; WordPress or another plugin handles image processing.

4. Regenerate image-size derivatives when needed

Regenerate thumbnails only when the source upload is correct but a WordPress image size is missing, stale, or unsuitable—for example, after a theme changes its image dimensions. Regeneration creates derivatives from existing media; it does not replace the original image, change which image is featured, or fetch a fresh website screenshot.

1. Check the image sizes configured in WordPress Media settings and the size selected by the directory card.
2. Confirm that the original listing image is correct in the Media Library.
3. Use a thumbnail-regeneration plugin such as Regenerate Thumbnails to rebuild derivatives for the affected media. Follow the tool’s current instructions; its interface can change.
4. GeoDirectory’s changelog also records that a tool was added to regenerate thumbnails for post images. Its menu location depends on the installed version, so check that version’s documentation rather than relying on a fixed path.
5. After regeneration, clear relevant caches and inspect the rendered card at its actual display size.

If a regenerated image still looks wrong, the template may be requesting a different size or applying a crop. GeoDirectory’s performance guidance describes using GD Post Meta for a single image with the image set to thumbnail in an archive item; that is a rendering choice, not a screenshot refresh control.

5. Clear the cache layers that can preserve an old image

A correct source image can coexist with a stale page. Clear caches after fixing a source or regenerating derivatives, working from the layers your site uses:

1. Clear the directory or page-cache plugin’s cache for the affected listing and archive.
2. Clear your host’s server cache if enabled.
3. Purge the CDN cache for the page or image URL if your CDN caches it.
4. Reload the listing and archive in a private window, or clear the browser cache.

For example, GeoDirectory’s instructions for WP Super Cache give the path WordPress → Settings → WP Super Cache → Delete Cache. That applies to WP Super Cache; other plugins and hosts have different controls. GeoDirectory advises checking plugin, server, and browser caches and contacting the host when server caching is managed by the host.

6. Verify which layer is still wrong

1. Open the listing and the directory archive after clearing caches.
2. Check the image’s source URL and compare it with the expected upload or screenshot.
3. If the source itself is wrong, fix the listing image, URL, field configuration, or capture setup.
4. If the source is right but the card is wrong, inspect the archive template’s image field, selected size, and crop settings.
5. If only a previously visited page is stale, purge the cache layer serving that page or image.

Change one layer at a time when diagnosing a batch of listings. That makes it easier to tell whether the issue is the source, image derivative, card template, or cache.

Or skip the browser setup

If your task is to capture a fresh website preview yourself, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns an image or PDF; the parameter names used by other screenshot APIs also work. See the ScreenshotNeo API documentation for options and setup.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up free and get 1,000 screenshots a month with no card.

Troubleshooting

Symptom	Likely cause	What to do
Screenshot still shows the previous website	Stale capture, wrong listing URL, or cached preview	Verify the URL and screenshot-field setup; check the plugin’s current recapture method; purge relevant caches.
Regeneration finishes but the website preview is unchanged	The preview is a remote screenshot, not a WordPress derivative	Use the plugin’s screenshot workflow or its support documentation; regeneration only rebuilds local image sizes.
Listing shows the wrong uploaded image	Another image is first, a logo/custom field is selected, or a fallback is active	Check image order, display settings, custom fields, and fallback sources.
Image remains blurry after regeneration	The selected size is too small, the theme requests another size, or the card crops it	Check Media settings and the archive template’s selected size and crop.
Listing is correct but archive card is old	Cached archive output or a different archive template field	Clear plugin, host, and CDN caches; inspect the card template if the stale result persists.
Screenshot is blank or shows a challenge page	The external site may be unavailable, restricted, or presenting a bot check	Open the URL directly, confirm it is public, and consult the plugin or capture provider’s guidance.
Cache purge control is missing	The host or CDN manages caching outside WordPress	Check the host/CDN dashboard or contact the host for its purge instructions.

Performance, reliability, and cost considerations

• Regeneration scope: rebuild only affected images where the tool allows it. A large media library takes more processing and can add load while derivatives are generated.
• Capture scope: remote screenshots depend on the target site responding and permitting the capture mechanism. The GeoDirectory materials reviewed do not establish a universal retry policy or recapture interval.
• Cache freshness: cache purges improve freshness but may temporarily increase origin requests as pages and images are fetched again.
• Storage: additional image sizes consume media storage. Review the sizes your theme and templates actually use before adding more.
• Cost: WordPress thumbnail regeneration is a software operation; remote screenshot capture may be provided by the directory plugin or an external service with its own terms. Verify those terms for your installation. ScreenshotNeo offers 1,000 shots per month free with no card; paid plans are $5 for 3,000, $15 for 15,000, $39 for 60,000, $99 for 250,000, and $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan.

Frequently asked questions

Will regenerating thumbnails recapture every listing website?

No. It rebuilds WordPress image-size derivatives from images already stored in the media library. Remote website screenshots require the directory plugin’s screenshot workflow or a capture service.

Why does one listing show a placeholder while others work?

That listing may lack the selected image source, or its configured fallback chain may end at a placeholder. Check its logo, uploaded images, custom fields, and default images.

Can I follow GeoDirectory’s steps in any directory plugin?

No. GeoDirectory is an example with documented image behavior. Confirm the field names, refresh controls, and cache behavior for your own plugin and version.

How can I tell whether the image or page is cached?

Compare the image source URL with the rendered card after a cache purge. A correct source with an old card points toward page caching or template selection; an incorrect source points toward listing data or capture setup.