Kini, kami hadir di LinkedIn: Untuk mendapatkan berita dan referensi dari Google Penelusuran tentang cara membuat situs Anda dapat ditemukan, ikuti kami di LinkedIn.
Kami selalu tertarik dengan masukan yang kami terima. Kami juga melihat banyak permintaan untuk melengkapi pembaruan ini dengan menambahkan opsi pencocokan negatif
ke filter ekspresi reguler (regex).
Kabar baiknya, mulai hari ini filter laporan Performa mendukung filter ekspresi reguler baik yang cocok maupun tidak cocok. Opsi
tersedia di dropdown sekunder, yang muncul setelah memilih opsi "Kustom (ekspresi reguler)" di pemilih filter, seperti yang ditunjukkan pada screenshot
di bawah. Pelajari lebih lanjut cara memfilter data performa penelusuran.
Tips ringkas mengenai cara menggunakan ekspresi reguler di Search Console
Tips ringkas berikut dapat membantu jika Anda baru mempelajari cara menggunakan ekspresi reguler.
Pertama-tama, apa yang dimaksud dengan ekspresi reguler? Singkatnya, ekspresi reguler adalah urutan karakter yang menentukan pola penelusuran. Anda dapat menggunakannya
untuk membuat filter lanjutan guna menyertakan atau mengecualikan lebih dari sekadar kata atau frasa. Saat menggunakan ekspresi reguler, Anda dapat menggunakan sejumlah karakter meta, yakni
karakter yang memiliki makna khusus, misalnya untuk menentukan kriteria penelusuran. Lihat referensi sintaksis
ekspresi reguler RE2 untuk referensi terkait semua karakter meta yang didukung oleh Search Console.
Jika Anda belum tahu, berikut beberapa contoh terkait kapan harus menggunakan ekspresi reguler, bukan filter lain:
Menetapkan segmentasi pengguna yang sudah mengetahui merek Anda - Gunakan ekspresi reguler yang menentukan beberapa varian dari nama perusahaan Anda,
termasuk varian nama yang salah ketik. Hal ini akan memberi tahu Anda jenis kueri apa yang digunakan di setiap grup dan bagian situs mana yang menarik perhatian setiap audiens.
Misalnya, jika nama perusahaan Anda Willow Tree, sebaiknya Anda membuat filter untuk semua varian seperti
ini: willow tree|wilow tree|willowtree|willowtee (karakter meta | mewakili pernyataan OR).
Menganalisis traffic ke bagian situs - Gunakan ekspresi reguler yang berfokus pada direktori tertentu di situs Anda. Tindakan ini dapat membantu Anda
memahami apa saja kueri umum di setiap area konten. Misalnya, jika struktur URL Anda example.com/[product]/[brand]/[size]/[color]
dan ingin melihat traffic yang mengarah ke sepatu hijau, terlepas dari merek atau ukurannya, Anda dapat menggunakan shoes/.*/green
(.* cocok dengan karakter apa pun beberapa kali).
Memahami maksud pengguna - Gunakan ekspresi reguler untuk menganalisis jenis kueri apa yang membawa pengguna ke berbagai bagian situs Anda.
Misalnya, Anda mungkin tertarik dengan kueri yang berisi kata pertanyaan; filter kueri what|how|when|why mungkin
menampilkan hasil yang menunjukkan bahwa konten Anda dapat menjawab pertanyaan tersebut dengan mudah, mungkin melalui FAQ. Contoh lain adalah kueri yang berisi (atau tidak berisi)
kata transaksional seperti buy|purchase|order. Kueri ini mungkin juga menampilkan nama produk mana yang lebih umum atau jarang digunakan
dengan ekspresi tersebut.
Lihat pusat bantuan Search Console untuk mengetahui ekspresi
reguler umum. Jika Anda memiliki contoh penggunaan ekspresi reguler yang keren, bagikan di Twitter menggunakan hashtag #performanceregex.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],[],[[["\u003cp\u003eGoogle Search Console's Performance report now supports negative matching for regular expression filters, allowing users to exclude specific patterns.\u003c/p\u003e\n"],["\u003cp\u003eRegular expressions (regex) are sequences of characters used for advanced filtering beyond simple keywords, enabling analysis of various aspects of website traffic.\u003c/p\u003e\n"],["\u003cp\u003eRegex in Search Console can be used for tasks like segmenting users based on brand knowledge, analyzing traffic to specific website sections, and understanding user intent through query patterns.\u003c/p\u003e\n"],["\u003cp\u003eUsers can leverage the RE2 regex syntax and refer to Search Console help center for guidance on using regular expressions effectively.\u003c/p\u003e\n"]]],["The Search Console Performance report now supports both matching and non-matching regular expression (regex) filters via a secondary dropdown. Regex allows for advanced filtering using metacharacters, enabling users to segment branded traffic, analyze specific website sections (e.g., using `shoes/.*/green`), and understand user intent by filtering for question words or transactional terms (e.g `buy|purchase|order`). The document provides guidance, a link to the RE2 syntax, and encourages the sharing of regex examples.\n"],null,["# Search Console regex filters update and quick tips\n\nWednesday, June 02, 2021\n\n\nWe recently announced [improved data filtering](/search/blog/2021/04/performance-report-data-filtering)\nfor Search Console Performance reports, and we were delighted to see the [community\nreaction](https://twitter.com/googlesearchc/status/1379775388193320962) to the announcement.\n\n\nWe were also interested in the feedback we received, as always, and we saw many requests to complete the picture by adding a negative match option\nto the regular expression (regex) filter.\n\n\nThe good news is that starting today **the Performance report filter supports both matching and not matching regex filters** . The option\nis available through a secondary dropdown, which appears after picking the \"Custom (regex)\" option in the filter selector, as shown in the screenshot\nbelow. Learn more about [filtering search performance data](https://support.google.com/webmasters/answer/7576553#filteringdata).\n\n\nQuick tips on using regex on Search Console\n-------------------------------------------\n\n\nWe also thought it would be helpful to provide some quick tips if you're just starting with regex.\n\n\nFirst of all, what *is* a regular expression? In a few words, it is a sequence of characters that specifies a search pattern. You can use it\nto create advanced filters to include or exclude more than just a word or a phrase. When using regex, you can use a number of metacharacters, which are\ncharacters that have a special meaning, such as defining a search criteria. Check the [RE2 regex\nsyntax reference](https://github.com/google/re2/blob/main/doc/syntax.txt) for a reference on all metacharacters supported by Search Console.\n\n\nIf you're wondering when you should use regex as opposed to other filter types, here are a few examples when to use regex instead of other filters:\n\n- **Segment users that already know your brand** - Use regex that specify multiple variants of your company name, including misspellings. This will inform you what type of queries each group is using and which section of your website is attracting each audience. For example, if your company's names is `Willow Tree`, you might want to create a filter for all variants like this: `willow tree|wilow tree|willowtree|willowtee` (the `|` metacharacter represents an OR statement).\n- **Analyze traffic to a website section** - Use regex that focus on specific directories on your website, this can help you understand what are common queries for each of your content areas. For example, if your URL structure is `example.com/[product]/[brand]/[size]/[color]` and you'd like to view traffic leading to green shoes, but you don't care about the brand or the size, you might use `shoes/.*/green` (`.*` matches any character any number of times).\n- **Understand user intent** - Use regex to analyze which types of queries are bringing users to different sections of your website. For example, you might be interested in queries containing question words; a query filter `what|how|when|why` might show results that indicate your content should easily answer questions, maybe through an FAQ. Another example would be queries containing (or not) transactional words such as `buy|purchase|order`. This might also show which product names are more commonly or rarely used with these expressions.\n\n\nCheck the Search Console help center for [common regular\nexpressions](https://support.google.com/webmasters/answer/7576553#regexp_glossary). If you have any cool examples of what to use regex for, share them on Twitter using the hashtag `#performanceregex`.\n\n\nIf you have any questions or concerns, please reach out on the [Google Search Central Community](https://support.google.com/webmasters/threads?thread_filter=(category:search_console)) or on [Twitter](https://twitter.com/googlesearchc).\n\n\nPosted by [Daniel Waisberg](https://www.danielwaisberg.com), Search Advocate"]]