New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| Caching 404 pages in WordPress helps to reduce server load by preventing the need for the server to fully process each request for a non-existent page. During DDOS attacks, this can significantly improve performance as it minimizes the resources consumed by the large volume of incoming fake requests. | Het cachen van 404 pagina's in WordPress helpt de server belasting te verminderen door te voorkomen dat de server elke aanvraag voor een niet-bestaande pagina volledig moet verwerken. Tijdens DDOS aanvallen kan dit de prestaties aanzienlijk verbeteren, omdat het de bronnen minimaliseert die worden verbruikt door de grote hoeveelheid binnenkomende nep aanvragen. | Details | |
Original current
Caching 404 pages in WordPress helps to reduce server load by preventing the need for the server to fully process each request for a non-existent page. During DDOS attacks, this can significantly improve performance as it minimizes the resources consumed by the large volume of incoming fake requests.
You have to log in to edit this translation. |
|||
| The Web Vitals module helps measure real user performance data, also known as RUM, in a manner that accurately aligns with Google's measurement methods. By analyzing detailed log entries, you can pinpoint the reasons why your Core Web Vitals may not be performing optimally. These logs are stored in your WordPress database. However, it is not advisable to keep logging all data long-term on a production installation. Instead, it should be used only for short-term monitoring to identify any issues. | De Web Vitals module helpt bij het meten van echte gebruiker prestatiegegevens, ook wel bekend als RUM, op een manier die nauwkeurig aansluit bij de meetmethoden van Google. Door gedetailleerde log vermeldingen te analyseren, kun je de redenen achterhalen waarom je Core Web Vitals mogelijk niet optimaal presteren. Deze logs worden opgeslagen in je WordPress database. Het is echter niet raadzaam om alle gegevens op lange termijn te blijven loggen op een productie-installatie. In plaats daarvan moet het alleen worden gebruikt voor kortetermijn monitoring om eventuele problemen te identificeren. | Details | |
Original current
The Web Vitals module helps measure real user performance data, also known as RUM, in a manner that accurately aligns with Google's measurement methods. By analyzing detailed log entries, you can pinpoint the reasons why your Core Web Vitals may not be performing optimally. These logs are stored in your WordPress database. However, it is not advisable to keep logging all data long-term on a production installation. Instead, it should be used only for short-term monitoring to identify any issues.
You have to log in to edit this translation. |
|||
| Enhance each processed SERP Query with information about search volumes, keyword difficulty, competition index, bid price, etc. Search volumes enhance SERP data, but are not required for core functionality of this module. We charged extra cent for each query to load this data. Volume data do not need to be updated so often as SERP data. Volume data are requested just for queries with status "Processed". We get the volume data inderectly from Google Ads service, where many types of queries are not supported and even we need to pay for such query, no data are returned. Not supported are queries referring to: Dangerous or derogatory content; Sexually explicit content; Compensated sexual acts; Child sexual abuse imagery; Mail-order brides; Shocking content; Sensitive events; Animal cruelty; Hacked political materials. Often we get no data about queries of type "People also ask" or "Question" intents, queries longer as 80 characters or 10 words. It can 1-2 days until volume data are loaded from URLsLab service to your WordPress database. | Verbeter elke verwerkte SERP zoekopdracht met informatie over zoekvolumes, keyword moeilijkheid, concurrentie-index, biedprijs, enz. Zoekvolumes verbeteren SERP gegevens, maar zijn niet vereist voor de core functionaliteit van deze module. We rekenen extra cent per query om deze gegevens te laden. Volume gegevens hoeven niet zo vaak bijgewerkt te worden als SERP gegevens. Volume gegevens worden alleen opgevraagd voor verwerkte zoekopdrachten. We krijgen de volume gegevens indirect van de Google Ads dienst, waar veel soorten zoekopdrachten niet worden ondersteund en zelfs als we voor zo'n zoekopdracht moeten betalen, worden er geen gegevens geretourneerd. Niet ondersteunde zoekopdrachten zijn onder andere: Gevaarlijke of beledigende inhoud; Seksueel expliciete inhoud; Betaalde seksuele handelingen; Afbeeldingen van kindermisbruik; Postorderbruiden; Schokkende inhoud; Gevoelige gebeurtenissen; Dierenmishandeling; Gehackte politieke materialen. Vaak krijgen we geen gegevens over zoekopdrachten van het type "Mensen vragen ook" of "Vraag" intenties, zoekopdrachten langer dan 80 tekens of 10 woorden. Het kan 1-2 dagen duren voordat volume gegevens zijn geladen vanuit de URLsLab dienst naar WordPress database. | Details | |
Original current
Enhance each processed SERP Query with information about search volumes, keyword difficulty, competition index, bid price, etc. Search volumes enhance SERP data, but are not required for core functionality of this module. We charged extra cent for each query to load this data. Volume data do not need to be updated so often as SERP data. Volume data are requested just for queries with status "Processed". We get the volume data inderectly from Google Ads service, where many types of queries are not supported and even we need to pay for such query, no data are returned. Not supported are queries referring to: Dangerous or derogatory content; Sexually explicit content; Compensated sexual acts; Child sexual abuse imagery; Mail-order brides; Shocking content; Sensitive events; Animal cruelty; Hacked political materials. Often we get no data about queries of type "People also ask" or "Question" intents, queries longer as 80 characters or 10 words. It can 1-2 days until volume data are loaded from URLsLab service to your WordPress database.
You have to log in to edit this translation. |
|||
| The URLsLab plugin performs a variety of tasks, including taking screenshots, processing text, and generating summaries. These tasks are executed in the background on our servers and later synced with your WordPress database. This table displays scheduled tasks set to crawl specific domains or URLs at predetermined intervals. Each task performed by the URLsLab Service uses credits from your account. Therefore, it is essential to strategically select the scanning intervals for data from defined URLs and the types of tasks, so that credits are used efficiently. | De URLsLab plugin voert verschillende taken uit, waaronder het maken van schermafbeeldingen, het verwerken van tekst en het genereren van samenvattingen. Deze taken worden op de achtergrond uitgevoerd op onze servers en later gesynchroniseerd met je WordPress database. In deze tabel worden geplande taken weergegeven die zijn ingesteld om specifieke domeinen of URL's op vooraf bepaalde tijdstippen te doorzoeken. Elke taak die wordt uitgevoerd door de URLsLab service gebruikt credits van je account. Het is daarom essentieel om strategisch de scan intervallen voor gegevens van gedefinieerde URL's en het type taken te selecteren, zodat credits efficiënt worden gebruikt. | Details | |
Original current
The URLsLab plugin performs a variety of tasks, including taking screenshots, processing text, and generating summaries. These tasks are executed in the background on our servers and later synced with your WordPress database. This table displays scheduled tasks set to crawl specific domains or URLs at predetermined intervals. Each task performed by the URLsLab Service uses credits from your account. Therefore, it is essential to strategically select the scanning intervals for data from defined URLs and the types of tasks, so that credits are used efficiently.
You have to log in to edit this translation. |
|||
| The table displays the charges deducted from your credit balance, categorized by transaction type and date. These charges are associated with tasks run by your API key. If multiple WordPress installations use the same API key, the table will also show the costs generated by all installations. | De tabel toont de kosten die zijn afgetrokken van je tegoed, gecategoriseerd op transactietype en datum. Deze kosten zijn gekoppeld aan taken die worden uitgevoerd met je API-sleutel. Als meerdere WordPress installaties dezelfde API-sleutel gebruiken, toont de tabel ook de kosten die worden gegenereerd door alle installaties. | Details | |
Original current
The table displays the charges deducted from your credit balance, categorized by transaction type and date. These charges are associated with tasks run by your API key. If multiple WordPress installations use the same API key, the table will also show the costs generated by all installations.
You have to log in to edit this translation. |
|||
| Optimize WordPress DB | Optimaliseer WordPress DB | Details | |
Original current
Optimize WordPress DB
You have to log in to edit this translation. |
|||
| Override the default caching behavior set in the Settings tab. These customizable rules allow you to fully manage the caching headers in your WordPress installation. You have the flexibility to establish varying cache validity across different parts of your website, adjust the values for each file type, and even alter caching based on specific cookie or HTTP header parameters. It's important to arrange these rules in the correct order (refer to the Order column) since the first rule that meets the condition will be implemented on the page, rendering subsequent rules redundant. Broad conditions should be placed at the end of the list, while specific ones should be positioned at the top for effective rule enforcement. | Overschrijf het standaard cache gedrag dat is ingesteld in de tab Instellingen. Met deze aanpasbare regels kun je het cache beheer volledig beheren in je WordPress installatie. Je hebt de flexibiliteit om verschillende cache geldigheid in te stellen voor verschillende delen van je site, de waarden aan te passen voor elk bestandstype en zelfs caching te wijzigen op basis van specifieke cookie- of HTTP headerparameters. Het is belangrijk om deze regels in de juiste volgorde te plaatsen (zie de kolom Volgorde), omdat de eerste regel die aan de voorwaarde voldoet, wordt toegepast op de pagina, waardoor volgende regels overbodig worden. Brede voorwaarden moeten aan het einde van de lijst worden geplaatst, terwijl specifieke voorwaarden bovenaan moeten staan voor effectieve handhaving van de regels. | Details | |
Original current
Override the default caching behavior set in the Settings tab. These customizable rules allow you to fully manage the caching headers in your WordPress installation. You have the flexibility to establish varying cache validity across different parts of your website, adjust the values for each file type, and even alter caching based on specific cookie or HTTP header parameters. It's important to arrange these rules in the correct order (refer to the Order column) since the first rule that meets the condition will be implemented on the page, rendering subsequent rules redundant. Broad conditions should be placed at the end of the list, while specific ones should be positioned at the top for effective rule enforcement.
You have to log in to edit this translation. |
|||
| The table displays a list of texts that have already been produced by the AI generator shortcode. When the shortcode is placed on a specific page, it initiates an AI task. The text created by the AI generator is then stored in the result entry and subsequently presented on the page. The WordPress page does not directly contain the text; instead, it is incorporated into the page as it is generated. The page only includes the shortcode, which is then replaced with the actual text. The text generated by AI can be edited, approved, or declined to prevent the page from being spammed with inaccurate texts. | De tabel toont een lijst met teksten die al zijn gegenereerd door de AI-generator shortcode. Wanneer de shortcode op een specifieke pagina wordt geplaatst, wordt er een AI taak gestart. De tekst die door de AI-generator is gemaakt, wordt vervolgens opgeslagen in de resultaat vermelding en vervolgens op de pagina weergegeven. De WordPress pagina bevat de tekst niet direct; in plaats daarvan wordt deze geïntegreerd in de pagina zoals deze wordt gegenereerd. De pagina bevat alleen de shortcode, die vervolgens wordt vervangen door de daadwerkelijke tekst. De tekst die door AI is gegenereerd, kan worden bewerkt, toegestaan of afgewezen om te voorkomen dat de pagina wordt overspoeld met onnauwkeurige teksten. | Details | |
Original current
The table displays a list of texts that have already been produced by the AI generator shortcode. When the shortcode is placed on a specific page, it initiates an AI task. The text created by the AI generator is then stored in the result entry and subsequently presented on the page. The WordPress page does not directly contain the text; instead, it is incorporated into the page as it is generated. The page only includes the shortcode, which is then replaced with the actual text. The text generated by AI can be edited, approved, or declined to prevent the page from being spammed with inaccurate texts.
You have to log in to edit this translation. |
|||
| The AI Generator shortcode defines the text generation process within a specific shortcode location. These shortcodes can be incorporated within a WordPress template or added as a single code to the page editor. As soon as the shortcode appears on the page and text is generated, it's replaced by the actual text. When the shortcode is displayed for the first time, it's replaced with empty text and a new generator task is dispatched to a queue. This process can take several days until all texts are created. In the Settings tab, there is an option to have all new text pending for approval or approved right away. To view entries with this status, simply use the filter. Approve each entry individually for them to appear on your website. If not approved, these texts won't be publicly visible on your site. | De AI generator shortcode definieert het proces van tekst generatie binnen een specifieke shortcode locatie. Deze shortcodes kunnen worden opgenomen in een WordPress template of toegevoegd worden als een enkele code aan de pagina bewerker. Zodra de shortcode op de pagina verschijnt en tekst wordt gegenereerd, wordt deze vervangen door de daadwerkelijke tekst. Wanneer de shortcode voor de eerste keer wordt weergegeven, wordt deze vervangen door lege tekst en wordt er een nieuwe generator taak naar een wachtrij gestuurd. Dit proces kan enkele dagen duren totdat alle teksten zijn gemaakt. In de tab Instellingen is er een optie om alle nieuwe tekst in afwachting van goedkeuring te houden of meteen goed te keuren. Om items met deze status te bekijken, kun je eenvoudig de filter gebruiken. Keur elk item afzonderlijk goed zodat ze op je site verschijnen. Als ze niet worden goedgekeurd, zijn deze teksten niet openbaar zichtbaar op je site. | Details | |
Original current
The AI Generator shortcode defines the text generation process within a specific shortcode location. These shortcodes can be incorporated within a WordPress template or added as a single code to the page editor. As soon as the shortcode appears on the page and text is generated, it's replaced by the actual text. When the shortcode is displayed for the first time, it's replaced with empty text and a new generator task is dispatched to a queue. This process can take several days until all texts are created. In the Settings tab, there is an option to have all new text pending for approval or approved right away. To view entries with this status, simply use the filter. Approve each entry individually for them to appear on your website. If not approved, these texts won't be publicly visible on your site.
You have to log in to edit this translation. |
|||
| After linking your Google Search Console to your account at www.urlslab.com, a list of Google Search Console properties will become visible in this table. You have the option to enable query imports for each property independently. Only import properties that are relevant to your current website. Domains from Google Search Console are stored in your local WordPress database. Our goal is to update the list of properties only every 15 minutes when you refresh this table. | Nadat je je Google Search Console hebt gekoppeld aan je account op www.urlslab.com, wordt er een lijst met Google Search Console eigenschappen zichtbaar in deze tabel. Je hebt de mogelijkheid om query-imports voor elke eigenschap afzonderlijk in te schakelen. Importeer alleen eigenschappen die relevant zijn voor je huidige website. Domeinen van Google Search Console worden opgeslagen in je lokale WordPress database. Ons doel is om de lijst met eigenschappen alleen bij te werken elke 15 minuten wanneer je deze tabel vernieuwt. | Details | |
Original current
After linking your Google Search Console to your account at www.urlslab.com, a list of Google Search Console properties will become visible in this table. You have the option to enable query imports for each property independently. Only import properties that are relevant to your current website. Domains from Google Search Console are stored in your local WordPress database. Our goal is to update the list of properties only every 15 minutes when you refresh this table.
You have to log in to edit this translation. |
|||
| Disable WordPress Lazy Loading | Schakel WordPress lazy-loading uit. | Details | |
Original current
Disable WordPress Lazy Loading
You have to log in to edit this translation. |
|||
| Mark URLs Processed by WordPress as Valid | Markeer URL's die verwerkt zijn door WordPress als geldig | Details | |
Original current
Mark URLs Processed by WordPress as Valid
You have to log in to edit this translation. |
|||
| When WordPress delivers an unvalidated URL, we'll deem it valid. | Wanneer WordPress een niet-gevalideerde URL levert, beschouwen we deze als geldig. | Details | |
Original current
When WordPress delivers an unvalidated URL, we'll deem it valid.
You have to log in to edit this translation. |
|||
| Background Offloading of WordPress Media | Achtergrond uitladen van WordPress media | Details | |
Original current
Background Offloading of WordPress Media
You have to log in to edit this translation. |
|||
| Offloading all media uploaded in WordPress in the background. | Achtergrond proces voor het uitladen van alle media die in WordPress zijn geüpload. | Details | |
Original current
Offloading all media uploaded in WordPress in the background.
You have to log in to edit this translation. |
|||
Export as